Project Number Date
test_Tails_ISO_stable 6110 31 Jan 2026, 07:42

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:49.452 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:3.518
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.116
When I start Tails from USB drive "old" with network unplugged 46.083
Then the boot device has safe access rights 2.577
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.325
After features/support/hooks.rb:100 0.006
Tags: @product
1:19.465
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 51.414
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 23.909
And I take note of which tps features are available 0.642
Then a Tails persistence partition exists on USB drive "old" 0.488
And I shutdown Tails and wait for the computer to power off 2.662
After features/support/hooks.rb:331 0.398
After features/support/hooks.rb:100 0.008
Tags: @product
1:21.970
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.659
Then Tails is running from USB drive "old" 0.219
And all tps features are active 0.994
When I write some files expected to persist 1.241
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
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.740
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 7.892
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.567
After features/support/hooks.rb:331 0.314
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.864
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.206
And I log in to a new session 10.186
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.677
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.329
Then the running Tails is installed on USB drive "to_upgrade" 14.962
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 2.084
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.355
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.928
Then all tps features from the old Tails version are active 0.905
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.407
And the expected persistent files created with the old Tails version are present in the filesystem 1.022
And all persistent directories from the old Tails version have safe access rights 1.823
After features/support/hooks.rb:331 0.930
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:31.183
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.934
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.016
And Tor is ready 12.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.313
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.292
Given I shutdown Tails and wait for the computer to power off 9.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.735
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.005
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.122
# 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.198
When the network is plugged 0.012
And Tor is ready 10.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.409
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.224
Given I shutdown Tails and wait for the computer to power off 7.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.480
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.041
And Tor is ready 10.558
Then the Upgrader considers the system as up-to-date 10.491
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:331 0.713
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.094
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.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 8.088
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.167
After features/support/hooks.rb:331 0.662
After features/support/hooks.rb:100 0.000