Project Number Date
test_Tails_ISO_stable 6192 10 Mar 2026, 14:41

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 14:6.114 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:28.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 15.152
When I start Tails from USB drive "old" with network unplugged 1:9.174
Then the boot device has safe access rights 2.888
And Tails is running from USB drive "old" 0.257
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.751
After features/support/hooks.rb:100 0.009
Tags: @product
1:36.743
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 1:0.487
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 26.113
And I take note of which tps features are available 0.857
Then a Tails persistence partition exists on USB drive "old" 0.652
And I shutdown Tails and wait for the computer to power off 8.266
After features/support/hooks.rb:331 0.277
After features/support/hooks.rb:100 0.006
Tags: @product
1:33.452
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.263
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.426
When I write some files expected to persist 1.443
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.471
And all persistent directories from the old Tails version have safe access rights 2.190
And I take note of which tps features are available 0.187
And I shutdown Tails and wait for the computer to power off 8.197
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.660
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.737
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 8.954
And I log in to a new session 14.820
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.925
And I plug USB drive "to_upgrade" 2.277
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.917
Then the running Tails is installed on USB drive "to_upgrade" 18.534
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:331 3.173
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.384
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.924
Then all tps features from the old Tails version are active 1.369
And Tails is running from USB drive "to_upgrade" 0.289
And the boot device has safe access rights 3.116
And the expected persistent files created with the old Tails version are present in the filesystem 1.355
And all persistent directories from the old Tails version have safe access rights 2.257
After features/support/hooks.rb:331 0.911
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:22.084
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 21.938
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.013
And Tor is ready 25.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.507
Given I shutdown Tails and wait for the computer to power off 15.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.465
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.295
When the network is plugged 0.015
And Tor is ready 40.226
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.490
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.161
Given I shutdown Tails and wait for the computer to power off 17.948
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.060
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.147
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.212
When the network is plugged 0.017
And Tor is ready 22.196
Then the Upgrader considers the system as up-to-date 0.123
# 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.874
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:331 0.968
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
28.717
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.383
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
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.051
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 19.513
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.402
After features/support/hooks.rb:331 0.716
After features/support/hooks.rb:100 0.000