Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 55 09 Jun 2026, 14:49

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 12:15.539 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:12.622
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 14.948
When I start Tails from USB drive "old" with network unplugged 52.606
Then the boot device has safe access rights 3.244
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:335 1.350
After features/support/hooks.rb:104 0.009
Tags: @product
1:36.433
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 59.831
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 27.019
And I take note of which tps features are available 0.453
Then a Tails persistence partition exists on USB drive "old" 0.624
And I shutdown Tails and wait for the computer to power off 8.202
After features/support/hooks.rb:335 0.423
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.793
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.899
Then Tails is running from USB drive "old" 0.234
And all tps features are active 1.177
When I write some files expected to persist 1.505
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.313
And all persistent directories from the old Tails version have safe access rights 2.478
And I take note of which tps features are available 0.245
And I shutdown Tails and wait for the computer to power off 8.445
# 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" 13.223
After features/support/hooks.rb:335 0.579
After features/support/hooks.rb:104 0.007
Tags: @product
2:15.977
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 8.773
And I log in to a new session 14.362
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.172
And I plug USB drive "to_upgrade" 2.291
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.398
Then the running Tails is installed on USB drive "to_upgrade" 16.687
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 3.004
After features/support/hooks.rb:104 0.000
Tags: @product
1:16.571
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.369
Then all tps features from the old Tails version are active 0.970
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.610
And the expected persistent files created with the old Tails version are present in the filesystem 1.300
And all persistent directories from the old Tails version have safe access rights 1.980
After features/support/hooks.rb:335 0.871
After features/support/hooks.rb:104 0.085
Tags: @product @automatic_upgrade
3:59.318
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.761
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.023
And Tor is ready 14.177
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.123
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.369
Given I shutdown Tails and wait for the computer to power off 9.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.125
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.271
And the file system changes introduced in version 6.2~testoverlayfs are present 0.277
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# 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.014
And Tor is ready 11.002
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.638
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.714
Given I shutdown Tails and wait for the computer to power off 7.585
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.129
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.197
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.015
And Tor is ready 11.563
Then the Upgrader considers the system as up-to-date 10.538
# 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.262
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:335 1.102
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
21.823
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.181
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.349
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.896
After features/support/hooks.rb:335 0.972
After features/support/hooks.rb:104 0.000