Project Number Date
test_Tails_ISO_stable 6260 03 Apr 2026, 11:25

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 14:31.511 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:44.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.774
When I start Tails from USB drive "old" with network unplugged 1:24.912
Then the boot device has safe access rights 3.037
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.759
After features/support/hooks.rb:100 0.040
Tags: @product
1:30.356
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 58.051
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 26.009
And I take note of which tps features are available 0.911
Then a Tails persistence partition exists on USB drive "old" 0.723
And I shutdown Tails and wait for the computer to power off 4.314
After features/support/hooks.rb:331 0.531
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.705
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.224
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.027
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 8.233
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.779
After features/support/hooks.rb:331 0.316
After features/support/hooks.rb:100 0.007
Tags: @product
2:25.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.233
And I log in to a new session 17.956
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.055
And I plug USB drive "to_upgrade" 2.278
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.932
Then the running Tails is installed on USB drive "to_upgrade" 17.451
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 0.804
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.629
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.177
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.623
And the expected persistent files created with the old Tails version are present in the filesystem 1.216
And all persistent directories from the old Tails version have safe access rights 2.227
After features/support/hooks.rb:331 0.626
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:16.550
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.819
And no SquashFS delta is installed 0.103
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.440
When the network is plugged 0.016
And Tor is ready 24.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.600
Given I shutdown Tails and wait for the computer to power off 20.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.788
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.337
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.174
# 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.323
When the network is plugged 0.017
And Tor is ready 20.676
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.474
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.257
Given I shutdown Tails and wait for the computer to power off 17.807
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.626
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.391
And the file system changes introduced in version 6.3~testoverlayfs are present 0.437
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.230
When the network is plugged 0.019
And Tor is ready 42.890
Then the Upgrader considers the system as up-to-date 0.123
# 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.924
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:331 0.975
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
50.693
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.235
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.396
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 41.361
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.543
After features/support/hooks.rb:331 0.595
After features/support/hooks.rb:100 0.000