Project Number Date
test_Tails_ISO_stable 6119 04 Feb 2026, 13:34

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:59.640 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:15.268
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.556
When I start Tails from USB drive "old" with network unplugged 55.802
Then the boot device has safe access rights 3.149
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 4.061
After features/support/hooks.rb:100 0.008
Tags: @product
1:31.930
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 57.747
Then Tails is running from USB drive "old" 0.261
And I create a persistent partition 28.034
And I take note of which tps features are available 0.859
Then a Tails persistence partition exists on USB drive "old" 0.686
And I shutdown Tails and wait for the computer to power off 4.279
After features/support/hooks.rb:331 0.468
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.900
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.359
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.049
When I write some files expected to persist 1.343
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.075
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 7.287
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.721
After features/support/hooks.rb:331 0.459
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.687
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 9.630
And I log in to a new session 12.432
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.209
And I plug USB drive "to_upgrade" 2.360
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.622
Then the running Tails is installed on USB drive "to_upgrade" 16.152
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 2.151
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.633
Then all tps features from the old Tails version are active 1.199
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.991
And the expected persistent files created with the old Tails version are present in the filesystem 1.341
And all persistent directories from the old Tails version have safe access rights 2.179
After features/support/hooks.rb:331 0.607
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
3:49.943
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.363
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.017
And Tor is ready 12.460
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.572
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.579
Given I shutdown Tails and wait for the computer to power off 9.768
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.843
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.628
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.347
When the network is plugged 0.017
And Tor is ready 10.240
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.481
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.763
Given I shutdown Tails and wait for the computer to power off 7.370
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.790
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.330
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.016
And Tor is ready 11.857
Then the Upgrader considers the system as up-to-date 10.679
# 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 5.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.560
After features/support/hooks.rb:331 1.115
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
22.243
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 7.874
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
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.018
And Tor is ready 10.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.076
After features/support/hooks.rb:331 1.076
After features/support/hooks.rb:100 0.000