Project Number Date
test_Tails_ISO_stable 6067 15 Jan 2026, 07:51

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 11:45.635 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
1:17.771
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.856
When I start Tails from USB drive "old" with network unplugged 58.722
Then the boot device has safe access rights 3.310
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.099
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.910
After features/support/hooks.rb:100 0.021
Tags: @product
1:23.823
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 54.368
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 23.685
And I take note of which tps features are available 0.637
Then a Tails persistence partition exists on USB drive "old" 0.513
And I shutdown Tails and wait for the computer to power off 4.237
After features/support/hooks.rb:331 0.583
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.063
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.801
Then Tails is running from USB drive "old" 0.301
And all tps features are active 1.475
When I write some files expected to persist 1.674
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.195
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 8.212
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.469
After features/support/hooks.rb:331 0.359
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.341
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.946
And I log in to a new session 11.428
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.763
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.964
Then the running Tails is installed on USB drive "to_upgrade" 15.736
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:331 4.069
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.155
Then all tps features from the old Tails version are active 1.101
And Tails is running from USB drive "to_upgrade" 0.383
And the boot device has safe access rights 2.603
And the expected persistent files created with the old Tails version are present in the filesystem 1.106
And all persistent directories from the old Tails version have safe access rights 1.808
After features/support/hooks.rb:331 1.012
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:24.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.158
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.022
And Tor is ready 13.507
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.074
Given I shutdown Tails and wait for the computer to power off 6.978
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.148
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.008
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.187
When the network is plugged 0.019
And Tor is ready 10.018
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.127
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.460
Given I shutdown Tails and wait for the computer to power off 7.972
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.391
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.336
And the file system changes introduced in version 6.3~testoverlayfs are present 0.419
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.047
And Tor is ready 10.071
Then the Upgrader considers the system as up-to-date 0.115
# 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 4.258
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.396
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
48.303
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.861
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 39.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 1.013
After features/support/hooks.rb:100 0.000