Project Number Date
test_Tails_ISO_21565-flatpak-safe 33 13 Sep 2026, 03:21

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:5.801 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:10.795
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.224
When I start Tails from USB drive "old" with network unplugged 53.987
Then the boot device has safe access rights 1.911
And Tails is running from USB drive "old" 0.204
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.149
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.719
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.940
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 47.209
Then Tails is running from USB drive "old" 0.172
And I create a persistent partition 23.215
And I take note of which tps features are available 6.150
Then a Tails persistence partition exists on USB drive "old" 0.484
And I shutdown Tails and wait for the computer to power off 2.633
After features/support/hooks.rb:339 0.389
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.597
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.429
Then Tails is running from USB drive "old" 0.228
And all tps features are active 6.606
When I write some files expected to persist 0.849
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.121
And all persistence configuration files have safe access rights 0.235
And all persistent directories from the old Tails version have safe access rights 1.483
And I take note of which tps features are available 5.909
And I shutdown Tails and wait for the computer to power off 2.530
# 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.113
After features/support/hooks.rb:339 0.198
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.780
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.396
And I log in to a new session 10.184
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.580
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.793
Then the running Tails is installed on USB drive "to_upgrade" 16.330
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.008
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.116
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.740
Then all tps features from the old Tails version are active 0.911
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 1.800
And the expected persistent files created with the old Tails version are present in the filesystem 0.961
And all persistent directories from the old Tails version have safe access rights 1.444
After features/support/hooks.rb:339 0.490
After features/support/hooks.rb:108 0.060
Tags: @product @automatic_upgrade
3:36.501
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.714
And no SquashFS delta is installed 0.045
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.200
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.240
When the network is plugged 0.035
And Tor is ready 12.859
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.884
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.047
Given I shutdown Tails and wait for the computer to power off 5.262
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.490
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.473
And the file system changes introduced in version 6.2~testoverlayfs are present 0.172
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# 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.145
When the network is plugged 0.026
And Tor is ready 16.082
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.848
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.307
Given I shutdown Tails and wait for the computer to power off 2.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.584
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.651
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.036
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.028
And Tor is ready 10.098
Then the Upgrader considers the system as up-to-date 10.388
# 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.054
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.892
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
18.068
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.648
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.031
And Tor is ready 8.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.005
After features/support/hooks.rb:339 0.610
After features/support/hooks.rb:108 0.000