Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 30 17 May 2026, 14:09

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:7.625 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.956
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
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" 12.986
When I start Tails from USB drive "old" with network unplugged 52.633
Then the boot device has safe access rights 2.560
And Tails is running from USB drive "old" 0.254
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 1.422
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.173
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 52.704
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 24.115
And I take note of which tps features are available 0.438
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 7.980
After features/support/hooks.rb:335 0.257
After features/support/hooks.rb:104 0.007
Tags: @product
1:17.550
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.160
Then Tails is running from USB drive "old" 0.254
And all tps features are active 1.189
When I write some files expected to persist 1.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 1.690
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 2.639
# 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.757
After features/support/hooks.rb:335 0.272
After features/support/hooks.rb:104 0.007
Tags: @product
2:8.983
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.732
And I log in to a new session 12.384
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.674
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.562
Then the running Tails is installed on USB drive "to_upgrade" 14.108
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:335 2.166
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.041
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 59.982
Then all tps features from the old Tails version are active 0.961
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.548
And the expected persistent files created with the old Tails version are present in the filesystem 1.207
And all persistent directories from the old Tails version have safe access rights 2.036
After features/support/hooks.rb:335 0.670
After features/support/hooks.rb:104 0.006
3:39.091
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.993
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.174
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300
When the network is plugged 0.015
And Tor is ready 13.703
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.423
Given I shutdown Tails and wait for the computer to power off 9.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.440
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.077
And the file system changes introduced in version 6.2~testoverlayfs are present 0.186
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.141
# 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.222
When the network is plugged 0.020
And Tor is ready 10.672
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.707
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.936
Given I shutdown Tails and wait for the computer to power off 7.850
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.648
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.446
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.016
And Tor is ready 12.307
Then the Upgrader considers the system as up-to-date 10.653
# 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.261
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:335 0.931
After features/support/hooks.rb:104 0.014
18.829
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.644
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.791
After features/support/hooks.rb:335 0.959
After features/support/hooks.rb:104 0.000