Project Number Date
test_Tails_ISO_stable 6608 26 Aug 2026, 13:56

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.208 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
58.579
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.047
When I start Tails from USB drive "old" with network unplugged 40.116
Then the boot device has safe access rights 2.572
And Tails is running from USB drive "old" 0.300
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.177
After features/support/hooks.rb:108 0.011
Tags: @product
1:25.989
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 50.171
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 24.229
And I take note of which tps features are available 6.640
Then a Tails persistence partition exists on USB drive "old" 0.477
And I shutdown Tails and wait for the computer to power off 4.027
After features/support/hooks.rb:339 0.325
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.480
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.637
Then Tails is running from USB drive "old" 0.257
And all tps features are active 7.844
When I write some files expected to persist 1.129
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.127
And all persistence configuration files have safe access rights 0.237
And all persistent directories from the old Tails version have safe access rights 1.536
And I take note of which tps features are available 6.328
And I shutdown Tails and wait for the computer to power off 2.763
# 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.529
After features/support/hooks.rb:339 0.330
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.548
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 without a persistent partition and stopped at Tails Greeter's login screen 8.565
And I log in to a new session 11.984
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.849
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.901
Then the running Tails is installed on USB drive "to_upgrade" 18.764
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.112
After features/support/hooks.rb:339 3.526
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.669
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.580
Then all tps features from the old Tails version are active 1.218
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.663
And the expected persistent files created with the old Tails version are present in the filesystem 1.115
And all persistent directories from the old Tails version have safe access rights 1.780
After features/support/hooks.rb:339 0.527
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:51.870
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.607
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.026
And Tor is ready 12.680
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.955
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.419
Given I shutdown Tails and wait for the computer to power off 6.880
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.284
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 8.474
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.198
When the network is plugged 0.038
And Tor is ready 10.388
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.070
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.359
Given I shutdown Tails and wait for the computer to power off 4.114
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.729
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.669
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.097
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.034
And Tor is ready 11.030
Then the Upgrader considers the system as up-to-date 10.477
# 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.766
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:339 1.006
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
20.071
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.845
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.034
And Tor is ready 8.741
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.142
After features/support/hooks.rb:339 0.807
After features/support/hooks.rb:108 0.000