Project Number Date
test_Tails_ISO_21565-flatpak-safe 25 04 Sep 2026, 03:20

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:52.786 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.159
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.053
When I start Tails from USB drive "old" with network unplugged 48.611
Then the boot device has safe access rights 1.824
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 1.864
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 47.858
Then Tails is running from USB drive "old" 0.192
And I create a persistent partition 22.778
And I take note of which tps features are available 5.831
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 2.586
After features/support/hooks.rb:339 0.523
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.755
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.653
Then Tails is running from USB drive "old" 0.198
And all tps features are active 6.906
When I write some files expected to persist 1.015
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.262
And all persistent directories from the old Tails version have safe access rights 1.388
And I take note of which tps features are available 5.404
And I shutdown Tails and wait for the computer to power off 2.506
# 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.175
After features/support/hooks.rb:339 0.144
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.526
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.230
And I log in to a new session 10.714
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.601
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.212
Then the running Tails is installed on USB drive "to_upgrade" 17.243
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:339 1.856
After features/support/hooks.rb:108 0.000
Tags: @product
1:2.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 56.887
Then all tps features from the old Tails version are active 1.030
And Tails is running from USB drive "to_upgrade" 0.176
And the boot device has safe access rights 1.966
And the expected persistent files created with the old Tails version are present in the filesystem 0.791
And all persistent directories from the old Tails version have safe access rights 1.552
After features/support/hooks.rb:339 0.674
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:30.900
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 8.041
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.035
And Tor is ready 12.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.693
Given I shutdown Tails and wait for the computer to power off 5.216
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.303
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.405
And the file system changes introduced in version 6.2~testoverlayfs are present 0.143
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.110
# 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.214
When the network is plugged 0.034
And Tor is ready 9.952
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.498
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.369
Given I shutdown Tails and wait for the computer to power off 2.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.173
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.608
And the file system changes introduced in version 6.3~testoverlayfs are present 0.306
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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.123
When the network is plugged 0.031
And Tor is ready 9.945
Then the Upgrader considers the system as up-to-date 10.413
# 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 2.985
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.320
After features/support/hooks.rb:339 0.947
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.125
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.532
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.972
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.286
After features/support/hooks.rb:339 0.542
After features/support/hooks.rb:108 0.000