Project Number Date
test_Tails_ISO_stable 5960 19 Nov 2025, 12:35

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:25.723 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:0.305
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 30.210
When I start Tails from USB drive "old" with network unplugged 1:24.514
Then the boot device has safe access rights 3.223
And Tails is running from USB drive "old" 0.359
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:331 4.012
After features/support/hooks.rb:100 0.009
Tags: @product
2:6.682
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "old" with network unplugged and I login 1:26.426
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 29.811
And I take note of which tps features are available 1.352
Then a Tails persistence partition exists on USB drive "old" 0.701
And I shutdown Tails and wait for the computer to power off 7.886
After features/support/hooks.rb:331 0.412
After features/support/hooks.rb:100 0.017
Tags: @product
2:19.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.252
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.957
Then Tails is running from USB drive "old" 0.727
And all tps features are active 2.024
When I write some files expected to persist 1.681
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.353
And all persistent directories from the old Tails version have safe access rights 2.277
And I take note of which tps features are available 0.461
And I shutdown Tails and wait for the computer to power off 8.728
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.294
After features/support/hooks.rb:331 0.506
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.827
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 without a persistent partition and stopped at Tails Greeter's login screen 11.810
And I log in to a new session 14.353
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.823
And I plug USB drive "to_upgrade" 8.822
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.672
Then the running Tails is installed on USB drive "to_upgrade" 20.771
And I unplug USB drive "to_upgrade" 0.318
And I unplug USB drive "__internal" 0.255
After features/support/hooks.rb:331 3.580
After features/support/hooks.rb:100 0.000
Tags: @product
1:51.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.041
Then all tps features from the old Tails version are active 1.552
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.828
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.210
After features/support/hooks.rb:331 0.859
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:44.053
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.129
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
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.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.048
And Tor is ready 12.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.587
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.942
Given I shutdown Tails and wait for the computer to power off 9.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.804
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.907
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
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.147
# 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.260
When the network is plugged 0.054
And Tor is ready 12.632
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.599
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.781
Given I shutdown Tails and wait for the computer to power off 3.111
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.075
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.004
And the file system changes introduced in version 6.3~testoverlayfs are present 0.484
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.051
And Tor is ready 12.138
Then the Upgrader considers the system as up-to-date 0.229
# 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.444
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.542
After features/support/hooks.rb:331 1.109
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
28.278
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.836
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
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 8.132
And Tor is ready 8.309
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.609
After features/support/hooks.rb:331 1.124
After features/support/hooks.rb:100 0.000