Project Number Date
test_Tails_ISO_stable 5979 02 Dec 2025, 01:07

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 15:28.744 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.986
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 32.383
When I start Tails from USB drive "old" with network unplugged 1:23.107
Then the boot device has safe access rights 3.313
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 4.055
After features/support/hooks.rb:100 0.011
Tags: @product
2:7.350
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:27.755
Then Tails is running from USB drive "old" 0.588
And I create a persistent partition 29.323
And I take note of which tps features are available 1.151
Then a Tails persistence partition exists on USB drive "old" 0.632
And I shutdown Tails and wait for the computer to power off 7.728
After features/support/hooks.rb:331 0.785
After features/support/hooks.rb:100 0.022
Tags: @product
2:11.313
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.021
Given a computer 0.389
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.389
Then Tails is running from USB drive "old" 0.289
And all tps features are active 1.991
When I write some files expected to persist 1.995
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 2.626
And I take note of which tps features are available 0.521
And I shutdown Tails and wait for the computer to power off 7.899
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.684
After features/support/hooks.rb:331 0.165
After features/support/hooks.rb:100 0.010
Tags: @product
2:41.327
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 without a persistent partition and stopped at Tails Greeter's login screen 13.736
And I log in to a new session 17.162
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.363
And I plug USB drive "to_upgrade" 2.402
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.101
Then the running Tails is installed on USB drive "to_upgrade" 22.176
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:331 3.788
After features/support/hooks.rb:100 0.000
Tags: @product
1:26.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:17.292
Then all tps features from the old Tails version are active 1.582
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.148
And the expected persistent files created with the old Tails version are present in the filesystem 1.677
And all persistent directories from the old Tails version have safe access rights 2.323
After features/support/hooks.rb:331 0.979
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:37.789
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.123
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.435
When the network is plugged 0.060
And Tor is ready 14.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.771
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.543
Given I shutdown Tails and wait for the computer to power off 11.405
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.478
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.993
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.225
When the network is plugged 0.048
And Tor is ready 12.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.996
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.466
Given I shutdown Tails and wait for the computer to power off 7.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:26.655
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.221
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.298
When the network is plugged 0.071
And Tor is ready 11.768
Then the Upgrader considers the system as up-to-date 10.863
# 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.651
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.566
After features/support/hooks.rb:331 0.933
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
23.397
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 10.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 10.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.896
After features/support/hooks.rb:331 1.236
After features/support/hooks.rb:100 0.000