Project Number Date
test_Tails_ISO_flatpak-dsa-20260812 2 12 Aug 2026, 14: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:29.973 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:15.273
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.070
When I start Tails from USB drive "old" with network unplugged 56.891
Then the boot device has safe access rights 2.545
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.161
And I unplug USB drive "old" 0.102
After features/support/hooks.rb:339 3.715
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.313
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 48.144
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 23.317
And I take note of which tps features are available 8.475
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 2.585
After features/support/hooks.rb:339 0.541
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.321
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.208
Then Tails is running from USB drive "old" 0.223
And all tps features are active 7.752
When I write some files expected to persist 1.160
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.648
And I take note of which tps features are available 5.950
And I shutdown Tails and wait for the computer to power off 2.511
# 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" 11.274
After features/support/hooks.rb:339 0.487
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.210
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.597
And I log in to a new session 11.234
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.722
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.376
Then the running Tails is installed on USB drive "to_upgrade" 18.777
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 6.634
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.415
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.118
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.911
Then all tps features from the old Tails version are active 1.205
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.466
And the expected persistent files created with the old Tails version are present in the filesystem 0.986
And all persistent directories from the old Tails version have safe access rights 1.531
After features/support/hooks.rb:339 0.776
After features/support/hooks.rb:108 0.006
3:38.263
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.247
And no SquashFS delta is installed 0.088
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.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.293
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.028
And Tor is ready 10.825
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.634
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.131
Given I shutdown Tails and wait for the computer to power off 5.584
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.256
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.711
And the file system changes introduced in version 6.2~testoverlayfs are present 0.169
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.185
When the network is plugged 0.032
And Tor is ready 10.244
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.500
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.489
Given I shutdown Tails and wait for the computer to power off 2.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.439
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.152
And the file system changes introduced in version 6.3~testoverlayfs are present 0.400
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.030
And Tor is ready 10.140
Then the Upgrader considers the system as up-to-date 10.402
# 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 3.163
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.324
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.010
19.175
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.794
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
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.029
And Tor is ready 9.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.422
After features/support/hooks.rb:339 0.981
After features/support/hooks.rb:108 0.000