Project Number Date
test_Tails_ISO_stable 5975 28 Nov 2025, 21:49

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:22.474 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:9.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 33.231
When I start Tails from USB drive "old" with network unplugged 1:31.129
Then the boot device has safe access rights 2.902
And Tails is running from USB drive "old" 0.325
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.259
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 3.888
After features/support/hooks.rb:100 0.009
Tags: @product
2:5.426
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login 1:25.414
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 29.763
And I take note of which tps features are available 1.242
Then a Tails persistence partition exists on USB drive "old" 0.783
And I shutdown Tails and wait for the computer to power off 7.758
After features/support/hooks.rb:331 0.557
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.650
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.367
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.835
When I write some files expected to persist 1.618
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.297
And all persistent directories from the old Tails version have safe access rights 2.702
And I take note of which tps features are available 0.580
And I shutdown Tails and wait for the computer to power off 7.816
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.806
After features/support/hooks.rb:331 0.344
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.973
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 10.695
And I log in to a new session 16.131
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.974
And I plug USB drive "to_upgrade" 2.320
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.398
Then the running Tails is installed on USB drive "to_upgrade" 22.010
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:331 4.069
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.089
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 3.021
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.281
After features/support/hooks.rb:331 0.866
After features/support/hooks.rb:100 0.014
6:7.282
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.415
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.325
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.317
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.445
When the network is plugged 0.062
And Tor is ready 13.887
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.755
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.350
Given I shutdown Tails and wait for the computer to power off 11.637
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.404
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.194
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.269
When the network is plugged 0.111
And Tor is ready 41.127
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.585
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.458
Given I shutdown Tails and wait for the computer to power off 7.791
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.121
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 2.635
And the file system changes introduced in version 6.3~testoverlayfs are present 0.453
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.177
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.058
And Tor is ready 42.078
Then the Upgrader considers the system as up-to-date 0.260
# 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.773
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.565
After features/support/hooks.rb:331 1.095
After features/support/hooks.rb:100 0.021
23.666
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.008
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 12.535
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.607
After features/support/hooks.rb:331 0.667
After features/support/hooks.rb:100 0.000