Project Number Date
test_Tails_ISO_devel 4546 13 Aug 2026, 14:07

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:42.015 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:1.488
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.099
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.941
When I start Tails from USB drive "old" with network unplugged 43.532
Then the boot device has safe access rights 2.239
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.613
After features/support/hooks.rb:108 0.010
Tags: @product
1:25.814
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 50.937
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 23.546
And I take note of which tps features are available 6.403
Then a Tails persistence partition exists on USB drive "old" 0.502
And I shutdown Tails and wait for the computer to power off 4.046
After features/support/hooks.rb:339 0.486
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.336
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.015
Then Tails is running from USB drive "old" 0.262
And all tps features are active 7.780
When I write some files expected to persist 1.335
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.132
And all persistence configuration files have safe access rights 0.244
And all persistent directories from the old Tails version have safe access rights 1.707
And I take note of which tps features are available 5.761
And I shutdown Tails and wait for the computer to power off 2.601
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.363
After features/support/hooks.rb:339 0.484
After features/support/hooks.rb:108 0.007
Tags: @product
2:14.251
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.228
And I log in to a new session 12.782
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.616
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.293
Then the running Tails is installed on USB drive "to_upgrade" 18.810
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.158
After features/support/hooks.rb:339 2.069
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.958
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.806
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.421
Then all tps features from the old Tails version are active 1.168
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.545
And the expected persistent files created with the old Tails version are present in the filesystem 1.012
And all persistent directories from the old Tails version have safe access rights 1.749
After features/support/hooks.rb:339 0.740
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:54.508
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.564
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.037
And Tor is ready 18.162
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.023
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.579
Given I shutdown Tails and wait for the computer to power off 5.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.394
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.879
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.027
And Tor is ready 10.458
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.908
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.937
Given I shutdown Tails and wait for the computer to power off 4.124
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.671
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 8.925
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.173
When the network is plugged 0.029
And Tor is ready 10.268
Then the Upgrader considers the system as up-to-date 10.356
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 3.146
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.868
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
20.656
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.150
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 10.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.153
After features/support/hooks.rb:339 0.567
After features/support/hooks.rb:108 0.000