Project Number Date
test_Tails_ISO_21603-fragnesia 3 15 May 2026, 17:24

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:51.286 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
59.442
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 12.980
When I start Tails from USB drive "old" with network unplugged 41.998
Then the boot device has safe access rights 2.695
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.152
After features/support/hooks.rb:335 1.346
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.088
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 53.182
Then Tails is running from USB drive "old" 0.241
And I create a persistent partition 24.828
And I take note of which tps features are available 0.320
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 7.962
After features/support/hooks.rb:335 0.262
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.419
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.656
Then Tails is running from USB drive "old" 0.266
And all tps features are active 1.163
When I write some files expected to persist 1.274
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 1.769
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 7.818
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.794
After features/support/hooks.rb:335 0.407
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.188
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.358
And I log in to a new session 11.990
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.643
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.908
Then the running Tails is installed on USB drive "to_upgrade" 14.781
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:335 0.716
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.451
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.603
Then all tps features from the old Tails version are active 1.048
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 2.451
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.840
After features/support/hooks.rb:335 0.772
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:25.822
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.102
And no SquashFS delta is installed 0.061
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.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.013
And Tor is ready 12.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.940
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.529
Given I shutdown Tails and wait for the computer to power off 6.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.426
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.195
When the network is plugged 0.015
And Tor is ready 10.659
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.108
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.452
Given I shutdown Tails and wait for the computer to power off 4.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.182
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.106
And the file system changes introduced in version 6.3~testoverlayfs are present 0.358
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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.018
And Tor is ready 9.600
Then the Upgrader considers the system as up-to-date 10.529
# 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.756
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.383
After features/support/hooks.rb:335 0.616
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
18.873
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.256
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
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.017
And Tor is ready 9.626
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.651
After features/support/hooks.rb:335 0.911
After features/support/hooks.rb:104 0.000