Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 53 07 Jun 2026, 14:38

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:54.999 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.187
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.637
When I start Tails from USB drive "old" with network unplugged 1:6.616
Then the boot device has safe access rights 3.029
And Tails is running from USB drive "old" 0.288
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 3.475
After features/support/hooks.rb:104 0.038
Tags: @product
1:29.633
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 55.316
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 24.770
And I take note of which tps features are available 0.330
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 8.382
After features/support/hooks.rb:335 0.315
After features/support/hooks.rb:104 0.006
Tags: @product
1:29.511
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.518
Then Tails is running from USB drive "old" 0.312
And all tps features are active 1.255
When I write some files expected to persist 1.340
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.379
And all persistent directories from the old Tails version have safe access rights 1.850
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 7.882
# 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.569
After features/support/hooks.rb:335 0.306
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.084
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.093
And I log in to a new session 13.273
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.724
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.640
Then the running Tails is installed on USB drive "to_upgrade" 15.779
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:335 2.377
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.584
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.010
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.394
Then all tps features from the old Tails version are active 1.099
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.487
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 2.100
After features/support/hooks.rb:335 0.692
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:47.440
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 8.084
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.282
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.016
And Tor is ready 13.952
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.086
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.275
Given I shutdown Tails and wait for the computer to power off 9.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.104
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.437
And the file system changes introduced in version 6.2~testoverlayfs are present 0.339
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.235
When the network is plugged 0.025
And Tor is ready 10.981
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.057
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.051
Given I shutdown Tails and wait for the computer to power off 8.359
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.411
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.557
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.013
And Tor is ready 10.162
Then the Upgrader considers the system as up-to-date 10.714
# 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.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:335 1.041
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
19.556
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 7.568
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.761
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.875
After features/support/hooks.rb:335 0.711
After features/support/hooks.rb:104 0.000