Project Number Date
test_Tails_ISO_21565-flatpak-safe 128 05 Nov 2026, 19:37

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:41.709 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.469
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.728
When I start Tails from USB drive "old" with network unplugged 54.528
Then the boot device has safe access rights 2.331
And Tails is running from USB drive "old" 0.315
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 3.634
After features/support/hooks.rb:108 0.010
Tags: @product
1:27.961
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.143
And I start Tails from USB drive "old" with network unplugged and I login 50.039
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 23.824
And I take note of which tps features are available 7.676
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 5.456
After features/support/hooks.rb:339 0.341
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.063
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.965
Then Tails is running from USB drive "old" 0.200
And all tps features are active 8.410
When I write some files expected to persist 1.080
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.911
And I take note of which tps features are available 6.216
And I shutdown Tails and wait for the computer to power off 2.650
# 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.070
After features/support/hooks.rb:339 0.276
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.379
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 without a persistent partition and stopped at Tails Greeter's login screen 8.282
And I log in to a new session 12.493
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.606
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.348
Then the running Tails is installed on USB drive "to_upgrade" 18.165
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 2.391
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.669
Then all tps features from the old Tails version are active 1.160
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.426
And the expected persistent files created with the old Tails version are present in the filesystem 1.090
And all persistent directories from the old Tails version have safe access rights 2.207
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.061
3:40.976
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.607
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
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.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.367
When the network is plugged 0.029
And Tor is ready 13.660
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.339
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.737
Given I shutdown Tails and wait for the computer to power off 5.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.477
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.598
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.202
When the network is plugged 0.036
And Tor is ready 10.650
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.332
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.218
Given I shutdown Tails and wait for the computer to power off 3.947
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.062
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 10.445
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.029
And Tor is ready 10.990
Then the Upgrader considers the system as up-to-date 0.088
# 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.522
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.311
After features/support/hooks.rb:339 0.850
After features/support/hooks.rb:108 0.011
18.990
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.413
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.643
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.530
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.000