Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 52 06 Jun 2026, 14:26

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:38.149 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.110
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.864
When I start Tails from USB drive "old" with network unplugged 48.997
Then the boot device has safe access rights 2.496
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:335 3.532
After features/support/hooks.rb:104 0.027
Tags: @product
1:31.051
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 56.401
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 26.201
And I take note of which tps features are available 0.381
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 7.113
After features/support/hooks.rb:335 0.348
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.278
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.892
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.192
When I write some files expected to persist 1.276
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.049
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 8.523
# 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" 12.334
After features/support/hooks.rb:335 0.553
After features/support/hooks.rb:104 0.008
Tags: @product
2:12.722
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 without a persistent partition and stopped at Tails Greeter's login screen 8.262
And I log in to a new session 12.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.058
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.151
Then the running Tails is installed on USB drive "to_upgrade" 16.208
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.118
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.308
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.462
Then all tps features from the old Tails version are active 1.104
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 3.053
And the expected persistent files created with the old Tails version are present in the filesystem 1.348
And all persistent directories from the old Tails version have safe access rights 2.040
After features/support/hooks.rb:335 0.957
After features/support/hooks.rb:104 0.035
Tags: @product @automatic_upgrade
3:44.789
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 with a persistent partition enabled and logged in 8.141
And no SquashFS delta is installed 0.060
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.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.016
And Tor is ready 12.910
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.358
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.641
Given I shutdown Tails and wait for the computer to power off 8.433
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.623
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.218
When the network is plugged 0.017
And Tor is ready 11.238
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.561
Given I shutdown Tails and wait for the computer to power off 7.981
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.102
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.194
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.029
And Tor is ready 9.658
Then the Upgrader considers the system as up-to-date 10.541
# 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.367
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:335 0.679
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
21.888
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 7.462
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.746
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.328
After features/support/hooks.rb:335 0.871
After features/support/hooks.rb:104 0.000