Project Number Date
test_Tails_ISO_stable 5961 20 Nov 2025, 09:19

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:38.321 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:15.429
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 34.684
When I start Tails from USB drive "old" with network unplugged 1:35.341
Then the boot device has safe access rights 3.239
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.196
After features/support/hooks.rb:331 3.663
After features/support/hooks.rb:100 0.013
Tags: @product
2:24.409
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:39.652
Then Tails is running from USB drive "old" 0.659
And I create a persistent partition 33.880
And I take note of which tps features are available 1.273
Then a Tails persistence partition exists on USB drive "old" 0.804
And I shutdown Tails and wait for the computer to power off 7.975
After features/support/hooks.rb:331 1.365
After features/support/hooks.rb:100 0.016
Tags: @product
2:36.662
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.258
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:58.352
Then Tails is running from USB drive "old" 1.259
And all tps features are active 2.638
When I write some files expected to persist 1.895
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.448
And all persistent directories from the old Tails version have safe access rights 2.600
And I take note of which tps features are available 0.443
And I shutdown Tails and wait for the computer to power off 9.389
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.176
After features/support/hooks.rb:331 0.475
After features/support/hooks.rb:100 0.010
Tags: @product
2:43.398
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 18.393
And I log in to a new session 16.636
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.579
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.355
Then the running Tails is installed on USB drive "to_upgrade" 21.445
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.284
After features/support/hooks.rb:331 8.503
After features/support/hooks.rb:100 0.000
Tags: @product
1:57.100
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.419
Then all tps features from the old Tails version are active 1.473
And Tails is running from USB drive "to_upgrade" 0.321
And the boot device has safe access rights 4.059
And the expected persistent files created with the old Tails version are present in the filesystem 1.699
And all persistent directories from the old Tails version have safe access rights 2.901
After features/support/hooks.rb:331 1.023
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:17.668
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 12.501
And no SquashFS delta is installed 0.188
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.060
And Tor is ready 12.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.827
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.860
Given I shutdown Tails and wait for the computer to power off 9.671
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.597
Then Tails is running version 6.2~testoverlayfs 0.036
And all tps features are active 3.201
And the file system changes introduced in version 6.2~testoverlayfs are present 0.351
And only the 6.2~testoverlayfs SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.185
# 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.235
When the network is plugged 0.073
And Tor is ready 18.375
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.002
Given I shutdown Tails and wait for the computer to power off 7.626
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.181
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 2.752
And the file system changes introduced in version 6.3~testoverlayfs are present 0.441
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.234
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.301
When the network is plugged 0.061
And Tor is ready 12.174
Then the Upgrader considers the system as up-to-date 0.200
# 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 6.929
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.550
After features/support/hooks.rb:331 1.128
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
23.651
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.033
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.306
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 11.261
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.859
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.000