Project Number Date
test_Tails_ISO_stable 5971 27 Nov 2025, 08: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 17:40.807 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:58.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 36.995
When I start Tails from USB drive "old" with network unplugged 1:15.802
Then the boot device has safe access rights 3.099
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:331 5.815
After features/support/hooks.rb:100 0.008
Tags: @product
3:7.343
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 17.834
And I start Tails from USB drive "old" with network unplugged and I login 1:41.155
Then Tails is running from USB drive "old" 0.623
And I create a persistent partition 45.889
And I take note of which tps features are available 13.226
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 7.874
After features/support/hooks.rb:331 0.766
After features/support/hooks.rb:100 0.013
Tags: @product
2:34.484
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 5.611
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:38.758
Then Tails is running from USB drive "old" 0.777
And all tps features are active 14.646
When I write some files expected to persist 1.959
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.256
And all persistence configuration files have safe access rights 0.469
And all persistent directories from the old Tails version have safe access rights 2.870
And I take note of which tps features are available 0.572
And I shutdown Tails and wait for the computer to power off 9.226
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.334
After features/support/hooks.rb:331 0.177
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.994
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 11.001
And I log in to a new session 12.560
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.103
And I plug USB drive "to_upgrade" 3.632
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.172
Then the running Tails is installed on USB drive "to_upgrade" 21.143
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 3.986
After features/support/hooks.rb:100 0.000
Tags: @product
1:55.059
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.230
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.449
Then all tps features from the old Tails version are active 2.163
And Tails is running from USB drive "to_upgrade" 0.446
And the boot device has safe access rights 3.780
And the expected persistent files created with the old Tails version are present in the filesystem 1.900
And all persistent directories from the old Tails version have safe access rights 3.090
After features/support/hooks.rb:331 0.956
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
5:5.485
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.902
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.413
When the network is plugged 0.053
And Tor is ready 13.128
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.806
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.656
Given I shutdown Tails and wait for the computer to power off 7.856
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.995
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.671
And the file system changes introduced in version 6.2~testoverlayfs are present 0.432
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.282
When the network is plugged 0.066
And Tor is ready 12.724
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.702
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.689
Given I shutdown Tails and wait for the computer to power off 8.301
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.452
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.195
And the file system changes introduced in version 6.3~testoverlayfs are present 0.585
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.052
And Tor is ready 12.652
Then the Upgrader considers the system as up-to-date 0.198
# 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.673
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.555
After features/support/hooks.rb:331 0.967
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
24.413
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
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.065
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 10.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.648
After features/support/hooks.rb:331 1.055
After features/support/hooks.rb:100 0.000