Project Number Date
test_Tails_ISO_21565-flatpak-safe 109 28 Oct 2026, 19:44

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 12:20.012 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:26.411
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.445
When I start Tails from USB drive "old" with network unplugged 1:7.076
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.153
After features/support/hooks.rb:339 3.676
After features/support/hooks.rb:108 0.058
Tags: @product
1:28.878
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 52.087
Then Tails is running from USB drive "old" 0.236
And I create a persistent partition 26.465
And I take note of which tps features are available 6.885
Then a Tails persistence partition exists on USB drive "old" 0.490
And I shutdown Tails and wait for the computer to power off 2.628
After features/support/hooks.rb:339 0.567
After features/support/hooks.rb:108 0.009
Tags: @product
1:38.267
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.094
Then Tails is running from USB drive "old" 0.270
And all tps features are active 7.984
When I write some files expected to persist 1.384
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.360
And all persistent directories from the old Tails version have safe access rights 1.913
And I take note of which tps features are available 6.413
And I shutdown Tails and wait for the computer to power off 3.958
# 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.581
After features/support/hooks.rb:339 0.587
After features/support/hooks.rb:108 0.019
Tags: @product
2:17.545
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.031
And I log in to a new session 13.910
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.899
Then the running Tails is installed on USB drive "to_upgrade" 19.454
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 4.191
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.062
Then all tps features from the old Tails version are active 1.263
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.495
And the expected persistent files created with the old Tails version are present in the filesystem 1.291
And all persistent directories from the old Tails version have safe access rights 1.797
After features/support/hooks.rb:339 0.914
After features/support/hooks.rb:108 0.006
3:54.573
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 21.869
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.050
And Tor is ready 12.387
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.861
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.665
Given I shutdown Tails and wait for the computer to power off 5.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.068
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.408
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.182
When the network is plugged 0.032
And Tor is ready 10.802
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.879
Given I shutdown Tails and wait for the computer to power off 2.608
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.238
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.239
And the file system changes introduced in version 6.3~testoverlayfs are present 0.438
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.033
And Tor is ready 11.166
Then the Upgrader considers the system as up-to-date 0.115
# 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.668
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.013
21.024
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 12.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.399
After features/support/hooks.rb:339 0.714
After features/support/hooks.rb:108 0.000