Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 24 13 May 2026, 19:48

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:37.043 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:8.437
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.454
When I start Tails from USB drive "old" with network unplugged 50.446
Then the boot device has safe access rights 2.746
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 3.686
After features/support/hooks.rb:104 0.012
Tags: @product
1:33.869
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 57.088
Then Tails is running from USB drive "old" 0.256
And I create a persistent partition 27.291
And I take note of which tps features are available 0.395
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 8.198
After features/support/hooks.rb:335 0.529
After features/support/hooks.rb:104 0.009
Tags: @product
1:31.111
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 with persistence enabled 1:2.974
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.645
When I write some files expected to persist 1.385
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.314
And all persistent directories from the old Tails version have safe access rights 2.519
And I take note of which tps features are available 0.296
And I shutdown Tails and wait for the computer to power off 8.499
# 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.853
After features/support/hooks.rb:335 0.258
After features/support/hooks.rb:104 0.009
Tags: @product
2:11.430
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.623
And I log in to a new session 13.130
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.808
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.667
Then the running Tails is installed on USB drive "to_upgrade" 15.699
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.372
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.730
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.340
Then all tps features from the old Tails version are active 1.089
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.725
And the expected persistent files created with the old Tails version are present in the filesystem 1.346
And all persistent directories from the old Tails version have safe access rights 1.955
After features/support/hooks.rb:335 0.574
After features/support/hooks.rb:104 0.006
3:40.610
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.000
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.015
And Tor is ready 13.443
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.622
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.830
Given I shutdown Tails and wait for the computer to power off 9.894
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.959
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.174
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.228
When the network is plugged 0.017
And Tor is ready 10.177
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.171
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.222
Given I shutdown Tails and wait for the computer to power off 4.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.391
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.322
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.013
And Tor is ready 10.281
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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:335 0.811
After features/support/hooks.rb:104 0.011
19.854
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.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
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.050
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.943
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.492
After features/support/hooks.rb:335 0.893
After features/support/hooks.rb:104 0.000