Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 36 21 May 2026, 14:34

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:6.760 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:25.205
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.687
When I start Tails from USB drive "old" with network unplugged 1:6.843
Then the boot device has safe access rights 2.806
And Tails is running from USB drive "old" 0.251
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:335 1.416
After features/support/hooks.rb:104 0.009
Tags: @product
1:30.469
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 56.710
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 24.229
And I take note of which tps features are available 0.341
Then a Tails persistence partition exists on USB drive "old" 0.614
And I shutdown Tails and wait for the computer to power off 8.204
After features/support/hooks.rb:335 0.395
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.641
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.518
Then Tails is running from USB drive "old" 0.301
And all tps features are active 1.308
When I write some files expected to persist 1.326
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.245
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.028
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.208
# 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.103
After features/support/hooks.rb:335 0.203
After features/support/hooks.rb:104 0.008
Tags: @product
2:16.194
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.712
And I log in to a new session 13.352
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.909
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.283
Then the running Tails is installed on USB drive "to_upgrade" 18.394
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:335 2.494
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.468
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.519
Then all tps features from the old Tails version are active 1.226
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 2.835
And the expected persistent files created with the old Tails version are present in the filesystem 1.263
And all persistent directories from the old Tails version have safe access rights 2.250
After features/support/hooks.rb:335 0.776
After features/support/hooks.rb:104 0.026
Tags: @product @automatic_upgrade
3:48.616
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.161
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
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.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.015
And Tor is ready 12.903
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.658
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.940
Given I shutdown Tails and wait for the computer to power off 9.755
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.776
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.221
When the network is plugged 0.038
And Tor is ready 11.010
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.834
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.387
Given I shutdown Tails and wait for the computer to power off 8.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.640
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.385
And the file system changes introduced in version 6.3~testoverlayfs are present 0.436
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.164
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.018
And Tor is ready 9.909
Then the Upgrader considers the system as up-to-date 10.555
# 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.153
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.397
After features/support/hooks.rb:335 0.847
After features/support/hooks.rb:104 0.015
Tags: @product @automatic_upgrade
22.164
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 8.125
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.343
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.315
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.000