Project Number Date
test_Tails_ISO_stable 6605 25 Aug 2026, 11:35

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:2.775 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
56.281
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.202
When I start Tails from USB drive "old" with network unplugged 39.320
Then the boot device has safe access rights 2.047
And Tails is running from USB drive "old" 0.179
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.195
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.796
After features/support/hooks.rb:108 0.012
Tags: @product
1:22.869
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login 47.747
Then Tails is running from USB drive "old" 0.201
And I create a persistent partition 23.850
And I take note of which tps features are available 6.332
Then a Tails persistence partition exists on USB drive "old" 0.732
And I shutdown Tails and wait for the computer to power off 3.904
After features/support/hooks.rb:339 0.511
After features/support/hooks.rb:108 0.007
Tags: @product
1:35.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.194
Then Tails is running from USB drive "old" 0.241
And all tps features are active 7.328
When I write some files expected to persist 1.116
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.458
And I take note of which tps features are available 6.189
And I shutdown Tails and wait for the computer to power off 5.194
# 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" 11.922
After features/support/hooks.rb:339 0.580
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.621
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.220
And I log in to a new session 10.746
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.050
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.292
Then the running Tails is installed on USB drive "to_upgrade" 18.836
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 0.673
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.828
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.442
Then all tps features from the old Tails version are active 1.097
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.293
And the expected persistent files created with the old Tails version are present in the filesystem 1.185
And all persistent directories from the old Tails version have safe access rights 1.508
After features/support/hooks.rb:339 0.940
After features/support/hooks.rb:108 0.006
3:29.971
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.215
And no SquashFS delta is installed 0.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.163
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.199
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.307
When the network is plugged 0.034
And Tor is ready 12.120
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.621
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.492
Given I shutdown Tails and wait for the computer to power off 5.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.905
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.409
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.172
When the network is plugged 0.029
And Tor is ready 10.172
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.919
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.955
Given I shutdown Tails and wait for the computer to power off 3.892
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.249
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.498
And the file system changes introduced in version 6.3~testoverlayfs are present 0.389
And only the 6.3~testoverlayfs SquashFS delta is installed 0.030
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.168
When the network is plugged 0.032
And Tor is ready 11.060
Then the Upgrader considers the system as up-to-date 0.078
# 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.656
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.311
After features/support/hooks.rb:339 0.933
After features/support/hooks.rb:108 0.010
19.982
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.831
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 10.498
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.345
After features/support/hooks.rb:339 0.690
After features/support/hooks.rb:108 0.000