Project Number Date
test_Tails_ISO_stable 6075 17 Jan 2026, 11:40

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 10:46.208 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:10.381
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.263
When I start Tails from USB drive "old" with network unplugged 52.728
Then the boot device has safe access rights 2.586
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.085
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.759
After features/support/hooks.rb:100 0.068
Tags: @product
1:24.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 51.619
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 23.681
And I take note of which tps features are available 0.744
Then a Tails persistence partition exists on USB drive "old" 0.540
And I shutdown Tails and wait for the computer to power off 7.921
After features/support/hooks.rb:331 0.441
After features/support/hooks.rb:100 0.006
Tags: @product
1:21.667
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.278
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.053
When I write some files expected to persist 1.148
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.763
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 7.885
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.621
After features/support/hooks.rb:331 0.151
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.105
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 without a persistent partition and stopped at Tails Greeter's login screen 8.457
And I log in to a new session 10.023
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.761
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.227
Then the running Tails is installed on USB drive "to_upgrade" 15.111
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:331 6.792
After features/support/hooks.rb:100 0.000
Tags: @product
1:3.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.227
Then all tps features from the old Tails version are active 0.926
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.327
And the expected persistent files created with the old Tails version are present in the filesystem 1.003
And all persistent directories from the old Tails version have safe access rights 1.742
After features/support/hooks.rb:331 0.755
After features/support/hooks.rb:100 0.075
Tags: @product @automatic_upgrade
3:17.931
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 7.930
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.177
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.363
When the network is plugged 0.017
And Tor is ready 12.825
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.054
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.405
Given I shutdown Tails and wait for the computer to power off 9.350
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.105
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.025
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.172
When the network is plugged 0.016
And Tor is ready 10.796
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.152
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.071
Given I shutdown Tails and wait for the computer to power off 7.786
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.001
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.107
And the file system changes introduced in version 6.3~testoverlayfs are present 0.324
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.181
When the network is plugged 0.015
And Tor is ready 10.934
Then the Upgrader considers the system as up-to-date 0.111
# 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 3.801
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.316
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
18.735
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.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.047
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.008
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.000