Project Number Date
test_Tails_ISO_stable 5984 05 Dec 2025, 07:26

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:34.550 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.502
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 33.104
When I start Tails from USB drive "old" with network unplugged 1:21.664
Then the boot device has safe access rights 3.609
And Tails is running from USB drive "old" 0.314
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.226
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:331 4.173
After features/support/hooks.rb:100 0.014
Tags: @product
2:13.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login 1:30.367
Then Tails is running from USB drive "old" 0.829
And I create a persistent partition 30.889
And I take note of which tps features are available 1.548
Then a Tails persistence partition exists on USB drive "old" 1.358
And I shutdown Tails and wait for the computer to power off 8.219
After features/support/hooks.rb:331 0.288
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.066
Then Tails is running from USB drive "old" 0.656
And all tps features are active 1.927
When I write some files expected to persist 1.737
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.271
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.393
And I take note of which tps features are available 0.886
And I shutdown Tails and wait for the computer to power off 8.181
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.647
After features/support/hooks.rb:331 0.698
After features/support/hooks.rb:100 0.011
Tags: @product
2:35.019
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 10.233
And I log in to a new session 17.313
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.382
And I plug USB drive "to_upgrade" 2.730
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.871
Then the running Tails is installed on USB drive "to_upgrade" 21.942
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.316
After features/support/hooks.rb:331 4.079
After features/support/hooks.rb:100 0.000
Tags: @product
1:34.874
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.217
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:24.352
Then all tps features from the old Tails version are active 1.848
And Tails is running from USB drive "to_upgrade" 0.374
And the boot device has safe access rights 3.298
And the expected persistent files created with the old Tails version are present in the filesystem 1.852
And all persistent directories from the old Tails version have safe access rights 2.930
After features/support/hooks.rb:331 1.160
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
4:28.233
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.759
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.315
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.535
When the network is plugged 0.292
And Tor is ready 15.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.880
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.604
Given I shutdown Tails and wait for the computer to power off 11.194
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.157
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.634
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.235
# 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.730
When the network is plugged 0.074
And Tor is ready 12.241
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.622
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.232
Given I shutdown Tails and wait for the computer to power off 8.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.245
Then Tails is running version 6.3~testoverlayfs 0.024
And all tps features are active 2.566
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.050
And Tor is ready 13.631
Then the Upgrader considers the system as up-to-date 0.126
# 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.657
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.468
After features/support/hooks.rb:331 1.099
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
24.184
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.488
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
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.071
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 11.329
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.692
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.000