Project Number Date
test_Tails_ISO_21565-flatpak-safe 83 10 Oct 2026, 03:25

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:22.017 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:5.329
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.782
When I start Tails from USB drive "old" with network unplugged 47.262
Then the boot device has safe access rights 2.457
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.738
After features/support/hooks.rb:108 0.068
Tags: @product
1:25.169
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 49.188
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 24.177
And I take note of which tps features are available 6.826
Then a Tails persistence partition exists on USB drive "old" 0.603
And I shutdown Tails and wait for the computer to power off 4.039
After features/support/hooks.rb:339 0.225
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.466
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.924
Then Tails is running from USB drive "old" 0.174
And all tps features are active 7.720
When I write some files expected to persist 1.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 1.810
And I take note of which tps features are available 6.279
And I shutdown Tails and wait for the computer to power off 2.515
# 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.171
After features/support/hooks.rb:339 0.355
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.885
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.548
And I log in to a new session 12.226
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.708
And I plug USB drive "to_upgrade" 2.173
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.704
Then the running Tails is installed on USB drive "to_upgrade" 18.284
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.122
After features/support/hooks.rb:339 1.920
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.746
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.576
Then all tps features from the old Tails version are active 1.135
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.079
And the expected persistent files created with the old Tails version are present in the filesystem 0.879
And all persistent directories from the old Tails version have safe access rights 1.731
After features/support/hooks.rb:339 0.902
After features/support/hooks.rb:108 0.023
3:38.998
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 7.909
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.172
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.311
When the network is plugged 0.039
And Tor is ready 12.871
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.854
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.326
Given I shutdown Tails and wait for the computer to power off 5.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.449
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.617
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.169
# 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.163
When the network is plugged 0.028
And Tor is ready 10.476
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.855
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.529
Given I shutdown Tails and wait for the computer to power off 2.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.610
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 8.336
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.134
When the network is plugged 0.030
And Tor is ready 10.205
Then the Upgrader considers the system as up-to-date 10.443
# 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.190
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.341
After features/support/hooks.rb:339 0.859
After features/support/hooks.rb:108 0.011
18.420
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.576
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.176
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.025
And Tor is ready 9.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.984
After features/support/hooks.rb:339 0.778
After features/support/hooks.rb:108 0.000