Project Number Date
test_Tails_ISO_devel 4362 23 Apr 2026, 13:37

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:8.797 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:16.447
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.980
When I start Tails from USB drive "old" with network unplugged 56.202
Then the boot device has safe access rights 3.369
And Tails is running from USB drive "old" 0.309
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.235
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.347
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 56.020
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 25.359
And I take note of which tps features are available 0.705
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 4.503
After features/support/hooks.rb:331 0.542
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.201
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.338
When I write some files expected to persist 1.466
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.499
And all persistent directories from the old Tails version have safe access rights 1.997
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.192
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.362
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.006
Tags: @product
2:23.865
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.766
And I log in to a new session 18.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.221
And I plug USB drive "to_upgrade" 2.334
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.297
Then the running Tails is installed on USB drive "to_upgrade" 17.187
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 3.220
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.633
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:14.920
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.344
And all persistent directories from the old Tails version have safe access rights 2.705
After features/support/hooks.rb:331 0.720
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:32.383
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 9.549
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.041
And Tor is ready 44.682
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.461
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.741
Given I shutdown Tails and wait for the computer to power off 21.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.044
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.278
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.321
When the network is plugged 0.026
And Tor is ready 23.001
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.434
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.073
Given I shutdown Tails and wait for the computer to power off 18.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:25.443
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.476
And the file system changes introduced in version 6.3~testoverlayfs are present 0.423
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.025
And Tor is ready 22.784
Then the Upgrader considers the system as up-to-date 0.112
# 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.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:331 0.756
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
29.223
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 9.095
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 19.237
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.433
After features/support/hooks.rb:331 1.111
After features/support/hooks.rb:100 0.000