Project Number Date
test_Tails_ISO_21565-flatpak-safe 34 14 Sep 2026, 03:22

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:9.446 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:17.750
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.282
When I start Tails from USB drive "old" with network unplugged 1:0.939
Then the boot device has safe access rights 1.883
And Tails is running from USB drive "old" 0.178
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.163
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.637
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.929
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 46.585
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 22.802
And I take note of which tps features are available 6.225
Then a Tails persistence partition exists on USB drive "old" 0.476
And I shutdown Tails and wait for the computer to power off 2.534
After features/support/hooks.rb:339 0.428
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.428
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 with persistence enabled 57.434
Then Tails is running from USB drive "old" 0.214
And all tps features are active 6.541
When I write some files expected to persist 1.004
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.115
And all persistence configuration files have safe access rights 0.229
And all persistent directories from the old Tails version have safe access rights 1.315
And I take note of which tps features are available 5.925
And I shutdown Tails and wait for the computer to power off 2.529
# 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.034
After features/support/hooks.rb:339 0.381
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.620
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.254
And I log in to a new session 10.831
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.611
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.208
Then the running Tails is installed on USB drive "to_upgrade" 18.229
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.920
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.423
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.165
Then all tps features from the old Tails version are active 1.018
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 1.826
And the expected persistent files created with the old Tails version are present in the filesystem 0.730
And all persistent directories from the old Tails version have safe access rights 1.401
After features/support/hooks.rb:339 0.656
After features/support/hooks.rb:108 0.005
3:33.790
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 21.051
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.176
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.034
And Tor is ready 12.778
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.883
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.643
Given I shutdown Tails and wait for the computer to power off 5.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.002
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.253
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.174
When the network is plugged 0.035
And Tor is ready 10.094
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.486
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.439
Given I shutdown Tails and wait for the computer to power off 2.612
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.360
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.287
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.153
When the network is plugged 0.023
And Tor is ready 10.149
Then the Upgrader considers the system as up-to-date 0.102
# 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.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.010
18.503
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.720
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
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.037
And Tor is ready 9.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.866
After features/support/hooks.rb:339 0.710
After features/support/hooks.rb:108 0.000