Project Number Date
test_Tails_ISO_stable 5944 12 Nov 2025, 02:31

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 18:23.025 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:4.856
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 33.873
When I start Tails from USB drive "old" with network unplugged 1:25.925
Then the boot device has safe access rights 2.887
And Tails is running from USB drive "old" 0.292
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.254
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:331 3.780
After features/support/hooks.rb:100 0.011
Tags: @product
2:13.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.238
And I start Tails from USB drive "old" with network unplugged and I login 1:31.404
Then Tails is running from USB drive "old" 0.600
And I create a persistent partition 30.457
And I take note of which tps features are available 1.400
Then a Tails persistence partition exists on USB drive "old" 0.926
And I shutdown Tails and wait for the computer to power off 8.005
After features/support/hooks.rb:331 0.554
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.266
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.011
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.895
When I write some files expected to persist 1.571
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.397
And all persistence configuration files have safe access rights 0.701
And all persistent directories from the old Tails version have safe access rights 2.419
And I take note of which tps features are available 0.489
And I shutdown Tails and wait for the computer to power off 8.127
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.166
After features/support/hooks.rb:331 0.204
After features/support/hooks.rb:100 0.011
Tags: @product
2:46.922
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 without a persistent partition and stopped at Tails Greeter's login screen 13.269
And I log in to a new session 16.937
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.655
And I plug USB drive "to_upgrade" 2.538
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.848
Then the running Tails is installed on USB drive "to_upgrade" 22.282
And I unplug USB drive "to_upgrade" 0.192
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:331 4.121
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.562
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.183
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.754
Then all tps features from the old Tails version are active 1.987
And Tails is running from USB drive "to_upgrade" 0.323
And the boot device has safe access rights 3.404
And the expected persistent files created with the old Tails version are present in the filesystem 1.625
And all persistent directories from the old Tails version have safe access rights 2.283
After features/support/hooks.rb:331 0.942
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
6:15.821
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 13.780
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.310
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.436
When the network is plugged 0.067
And Tor is ready 13.962
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.041
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.141
Given I shutdown Tails and wait for the computer to power off 11.848
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.367
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
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.166
# 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.281
When the network is plugged 6.527
And Tor is ready 12.409
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.789
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 11.828
Given I shutdown Tails and wait for the computer to power off 11.703
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.643
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.498
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.185
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.051
And Tor is ready 18.491
Then the Upgrader considers the system as up-to-date 0.241
# 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 14.265
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.846
After features/support/hooks.rb:331 0.709
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
54.563
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 16.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 1.419
And Tor is ready 33.870
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.415
After features/support/hooks.rb:331 11.320
After features/support/hooks.rb:100 0.000