Project Number Date
test_Tails_ISO_stable 6153 18 Feb 2026, 08:47

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:9.142 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:9.269
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.224
When I start Tails from USB drive "old" with network unplugged 51.803
Then the boot device has safe access rights 2.395
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 3.819
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.168
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.889
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 23.922
And I take note of which tps features are available 0.681
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 7.880
After features/support/hooks.rb:331 0.164
After features/support/hooks.rb:100 0.006
Tags: @product
1:22.653
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.739
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.105
When I write some files expected to persist 1.216
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.789
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 7.847
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.895
After features/support/hooks.rb:331 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.276
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 without a persistent partition and stopped at Tails Greeter's login screen 8.520
And I log in to a new session 10.024
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.240
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.797
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.187
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.147
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.102
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.169
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.261
And the boot device has safe access rights 2.619
And the expected persistent files created with the old Tails version are present in the filesystem 1.196
And all persistent directories from the old Tails version have safe access rights 1.766
After features/support/hooks.rb:331 0.620
After features/support/hooks.rb:100 0.006
3:34.743
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.028
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.013
And Tor is ready 13.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.631
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.505
Given I shutdown Tails and wait for the computer to power off 11.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.331
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.108
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.200
When the network is plugged 0.012
And Tor is ready 10.855
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.795
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.473
Given I shutdown Tails and wait for the computer to power off 8.232
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.167
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.095
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.021
And Tor is ready 9.952
Then the Upgrader considers the system as up-to-date 10.502
# 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.363
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.011
19.882
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.501
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 8.125
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.964
After features/support/hooks.rb:331 0.845
After features/support/hooks.rb:100 0.000