Project Number Date
test_Tails_ISO_stable 5988 07 Dec 2025, 08:53

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 16:10.935 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
2:21.188
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.281
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 33.510
When I start Tails from USB drive "old" with network unplugged 1:41.584
Then the boot device has safe access rights 3.753
And Tails is running from USB drive "old" 0.308
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.261
After features/support/hooks.rb:331 3.869
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.540
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:29.707
Then Tails is running from USB drive "old" 0.795
And I create a persistent partition 30.639
And I take note of which tps features are available 1.353
Then a Tails persistence partition exists on USB drive "old" 0.723
And I shutdown Tails and wait for the computer to power off 7.145
After features/support/hooks.rb:331 0.501
After features/support/hooks.rb:100 0.012
Tags: @product
2:15.159
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:39.966
Then Tails is running from USB drive "old" 0.791
And all tps features are active 2.271
When I write some files expected to persist 1.623
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.443
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 7.610
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.195
After features/support/hooks.rb:331 0.428
After features/support/hooks.rb:100 0.024
Tags: @product
2:43.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 13.033
And I log in to a new session 18.020
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.257
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.427
Then the running Tails is installed on USB drive "to_upgrade" 22.058
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 3.924
After features/support/hooks.rb:100 0.000
Tags: @product
1:31.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:20.802
Then all tps features from the old Tails version are active 3.271
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.212
And the expected persistent files created with the old Tails version are present in the filesystem 1.501
And all persistent directories from the old Tails version have safe access rights 2.410
After features/support/hooks.rb:331 0.767
After features/support/hooks.rb:100 0.093
4:42.745
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.839
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.441
When the network is plugged 0.833
And Tor is ready 17.507
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.905
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.302
Given I shutdown Tails and wait for the computer to power off 9.902
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.105
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.066
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.161
# 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.258
When the network is plugged 0.065
And Tor is ready 12.524
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.670
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.829
Given I shutdown Tails and wait for the computer to power off 8.898
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.581
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.518
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.189
And Tor is ready 11.880
Then the Upgrader considers the system as up-to-date 10.674
# 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 6.985
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.477
After features/support/hooks.rb:331 1.305
After features/support/hooks.rb:100 0.097
25.853
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.029
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.300
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 13.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.568
After features/support/hooks.rb:331 1.041
After features/support/hooks.rb:100 0.000