Project Number Date
test_Tails_ISO_stable 6240 27 Mar 2026, 11:02

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 12:45.441 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.490
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.854
When I start Tails from USB drive "old" with network unplugged 1:0.213
Then the boot device has safe access rights 2.666
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 1.606
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.016
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.910
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 25.088
And I take note of which tps features are available 0.714
Then a Tails persistence partition exists on USB drive "old" 0.884
And I shutdown Tails and wait for the computer to power off 8.097
After features/support/hooks.rb:331 0.314
After features/support/hooks.rb:100 0.009
Tags: @product
1:24.717
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.235
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.070
When I write some files expected to persist 1.321
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.029
And I take note of which tps features are available 0.141
And I shutdown Tails and wait for the computer to power off 3.923
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.032
After features/support/hooks.rb:331 0.124
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.850
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.511
And I log in to a new session 13.098
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.931
And I plug USB drive "to_upgrade" 2.345
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.144
Then the running Tails is installed on USB drive "to_upgrade" 16.539
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 2.804
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.518
Then all tps features from the old Tails version are active 1.017
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.693
And the expected persistent files created with the old Tails version are present in the filesystem 1.150
And all persistent directories from the old Tails version have safe access rights 2.275
After features/support/hooks.rb:331 0.714
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:40.568
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.594
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.014
And Tor is ready 21.268
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.335
Given I shutdown Tails and wait for the computer to power off 20.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.071
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.148
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.202
When the network is plugged 0.017
And Tor is ready 21.011
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.406
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.394
Given I shutdown Tails and wait for the computer to power off 17.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.990
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.263
And the file system changes introduced in version 6.3~testoverlayfs are present 0.393
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.016
And Tor is ready 20.991
Then the Upgrader considers the system as up-to-date 0.113
# 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 5.106
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:331 0.983
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.743
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.039
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 18.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.355
After features/support/hooks.rb:331 1.160
After features/support/hooks.rb:100 0.000