Project Number Date
test_Tails_ISO_stable 6202 14 Mar 2026, 11: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 13:37.512 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:34.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.272
When I start Tails from USB drive "old" with network unplugged 1:15.465
Then the boot device has safe access rights 3.068
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:331 1.768
After features/support/hooks.rb:100 0.028
Tags: @product
1:35.296
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login 1:0.826
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 24.777
And I take note of which tps features are available 0.743
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 8.009
After features/support/hooks.rb:331 0.655
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.737
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.334
When I write some files expected to persist 1.380
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.475
And all persistent directories from the old Tails version have safe access rights 2.172
And I take note of which tps features are available 0.219
And I shutdown Tails and wait for the computer to power off 8.449
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.018
After features/support/hooks.rb:331 0.578
After features/support/hooks.rb:100 0.006
Tags: @product
2:22.132
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 without a persistent partition and stopped at Tails Greeter's login screen 8.949
And I log in to a new session 13.209
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.765
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.955
Then the running Tails is installed on USB drive "to_upgrade" 17.694
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 3.955
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.584
Then all tps features from the old Tails version are active 1.254
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.780
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.077
After features/support/hooks.rb:331 0.956
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:51.199
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.841
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.379
When the network is plugged 0.060
And Tor is ready 22.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.451
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.333
Given I shutdown Tails and wait for the computer to power off 20.064
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.857
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.227
When the network is plugged 0.019
And Tor is ready 21.751
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.477
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.374
Given I shutdown Tails and wait for the computer to power off 17.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.739
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.300
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.027
And Tor is ready 20.806
Then the Upgrader considers the system as up-to-date 0.098
# 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.906
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.936
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.974
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.926
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.373
After features/support/hooks.rb:331 0.573
After features/support/hooks.rb:100 0.000