Project Number Date
test_Tails_ISO_post-rm-7.11 10 21 Aug 2026, 18:15

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:51.359 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:18.852
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 14.012
When I start Tails from USB drive "old" with network unplugged 1:0.324
Then the boot device has safe access rights 2.701
And Tails is running from USB drive "old" 0.217
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.967
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 51.088
Then Tails is running from USB drive "old" 0.190
And I create a persistent partition 25.034
And I take note of which tps features are available 7.757
Then a Tails persistence partition exists on USB drive "old" 0.583
And I shutdown Tails and wait for the computer to power off 2.638
After features/support/hooks.rb:339 0.484
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.828
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.488
Then Tails is running from USB drive "old" 0.401
And all tps features are active 7.655
When I write some files expected to persist 1.210
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 1.646
And I take note of which tps features are available 6.141
And I shutdown Tails and wait for the computer to power off 4.072
# 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.619
After features/support/hooks.rb:339 0.502
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.028
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.736
And I log in to a new session 12.266
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.856
And I plug USB drive "to_upgrade" 2.279
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.480
Then the running Tails is installed on USB drive "to_upgrade" 20.127
And I unplug USB drive "to_upgrade" 0.151
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 1.839
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.739
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.957
Then all tps features from the old Tails version are active 1.102
And Tails is running from USB drive "to_upgrade" 0.219
And the boot device has safe access rights 2.337
And the expected persistent files created with the old Tails version are present in the filesystem 0.837
And all persistent directories from the old Tails version have safe access rights 2.191
After features/support/hooks.rb:339 0.987
After features/support/hooks.rb:108 0.006
3:41.466
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.697
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.026
And Tor is ready 13.444
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.619
Given I shutdown Tails and wait for the computer to power off 5.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.924
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.099
And the file system changes introduced in version 6.2~testoverlayfs are present 0.169
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.083
# 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.141
When the network is plugged 0.030
And Tor is ready 11.528
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.334
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.450
Given I shutdown Tails and wait for the computer to power off 2.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.503
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 9.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.318
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.190
When the network is plugged 0.027
And Tor is ready 10.555
Then the Upgrader considers the system as up-to-date 0.085
# 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 4.103
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.337
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.010
20.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.789
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.000