Project Number Date
test_Tails_ISO_21565-flatpak-safe 59 29 Sep 2026, 03:12

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 10:58.060 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.923
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.172
When I start Tails from USB drive "old" with network unplugged 1:1.244
Then the boot device has safe access rights 1.835
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 1.697
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.421
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 46.484
Then Tails is running from USB drive "old" 0.173
And I create a persistent partition 22.503
And I take note of which tps features are available 6.115
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 2.569
After features/support/hooks.rb:339 0.413
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.643
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.617
Then Tails is running from USB drive "old" 0.191
And all tps features are active 6.285
When I write some files expected to persist 0.974
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.249
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.651
And I take note of which tps features are available 5.755
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" 10.990
After features/support/hooks.rb:339 0.158
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.104
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.320
And I log in to a new session 10.788
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.645
And I plug USB drive "to_upgrade" 2.180
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.267
Then the running Tails is installed on USB drive "to_upgrade" 17.651
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 1.652
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.462
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.071
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.940
Then all tps features from the old Tails version are active 0.937
And Tails is running from USB drive "to_upgrade" 0.188
And the boot device has safe access rights 1.883
And the expected persistent files created with the old Tails version are present in the filesystem 0.849
And all persistent directories from the old Tails version have safe access rights 1.591
After features/support/hooks.rb:339 0.714
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:20.368
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.136
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.157
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.287
When the network is plugged 0.032
And Tor is ready 12.728
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.839
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.323
Given I shutdown Tails and wait for the computer to power off 5.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.267
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.459
And the file system changes introduced in version 6.2~testoverlayfs are present 0.175
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.100
# 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.154
When the network is plugged 0.051
And Tor is ready 10.216
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.849
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.423
Given I shutdown Tails and wait for the computer to power off 2.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.094
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.576
And the file system changes introduced in version 6.3~testoverlayfs are present 0.291
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.031
And Tor is ready 10.019
Then the Upgrader considers the system as up-to-date 0.069
# 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.104
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.403
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
18.136
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.794
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.175
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.029
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.209
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.860
After features/support/hooks.rb:339 0.541
After features/support/hooks.rb:108 0.000