Project Number Date
test_Tails_ISO_stable 6076 18 Jan 2026, 11: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 10:58.247 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:7.710
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.378
When I start Tails from USB drive "old" with network unplugged 49.899
Then the boot device has safe access rights 2.649
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:331 3.958
After features/support/hooks.rb:100 0.037
Tags: @product
1:25.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.120
And I start Tails from USB drive "old" with network unplugged and I login 51.977
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 24.211
And I take note of which tps features are available 0.691
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 7.904
After features/support/hooks.rb:331 0.189
After features/support/hooks.rb:100 0.007
Tags: @product
1:22.951
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.482
Then Tails is running from USB drive "old" 0.237
And all tps features are active 1.092
When I write some files expected to persist 1.152
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.730
And I take note of which tps features are available 0.156
And I shutdown Tails and wait for the computer to power off 8.135
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.506
After features/support/hooks.rb:331 0.409
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.970
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.256
And I log in to a new session 9.689
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.660
Then the running Tails is installed on USB drive "to_upgrade" 15.145
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:331 7.308
After features/support/hooks.rb:100 0.000
Tags: @product
1:4.778
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.560
Then all tps features from the old Tails version are active 0.931
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.230
And the expected persistent files created with the old Tails version are present in the filesystem 0.972
And all persistent directories from the old Tails version have safe access rights 1.793
After features/support/hooks.rb:331 0.941
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
3:28.862
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 8.016
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.325
When the network is plugged 0.019
And Tor is ready 12.966
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.184
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.651
Given I shutdown Tails and wait for the computer to power off 9.291
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.491
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.117
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.213
When the network is plugged 0.015
And Tor is ready 10.707
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.734
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.028
Given I shutdown Tails and wait for the computer to power off 4.009
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.250
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 0.982
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.197
When the network is plugged 0.013
And Tor is ready 11.089
Then the Upgrader considers the system as up-to-date 10.512
# 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.141
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:331 0.910
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
19.281
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.765
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.766
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.000