Project Number Date
test_Tails_ISO_21565-flatpak-safe 19 30 Aug 2026, 03:19

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:54.539 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:6.310
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.843
When I start Tails from USB drive "old" with network unplugged 49.562
Then the boot device has safe access rights 2.147
And Tails is running from USB drive "old" 0.223
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.741
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.799
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 45.507
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 23.540
And I take note of which tps features are available 6.371
Then a Tails persistence partition exists on USB drive "old" 0.463
And I shutdown Tails and wait for the computer to power off 2.528
After features/support/hooks.rb:339 0.507
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.984
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 with persistence enabled 59.157
Then Tails is running from USB drive "old" 0.200
And all tps features are active 6.639
When I write some files expected to persist 1.221
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.455
And I take note of which tps features are available 5.960
And I shutdown Tails and wait for the computer to power off 2.559
# 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.200
After features/support/hooks.rb:339 0.285
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.105
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.191
And I log in to a new session 11.618
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.657
And I plug USB drive "to_upgrade" 2.187
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.783
Then the running Tails is installed on USB drive "to_upgrade" 17.410
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.876
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.815
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:0.914
Then all tps features from the old Tails version are active 1.022
And Tails is running from USB drive "to_upgrade" 0.192
And the boot device has safe access rights 2.096
And the expected persistent files created with the old Tails version are present in the filesystem 0.943
And all persistent directories from the old Tails version have safe access rights 1.560
After features/support/hooks.rb:339 0.922
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:24.359
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.018
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.173
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
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.324
When the network is plugged 0.035
And Tor is ready 13.196
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.948
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.705
Given I shutdown Tails and wait for the computer to power off 5.222
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.647
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 7.848
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.072
# 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.171
When the network is plugged 0.038
And Tor is ready 10.043
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.882
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.235
Given I shutdown Tails and wait for the computer to power off 4.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.839
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.267
And the file system changes introduced in version 6.3~testoverlayfs are present 0.249
And only the 6.3~testoverlayfs SquashFS delta is installed 0.029
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.125
When the network is plugged 0.027
And Tor is ready 10.037
Then the Upgrader considers the system as up-to-date 0.113
# 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.170
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.260
After features/support/hooks.rb:339 0.985
After features/support/hooks.rb:108 0.023
Tags: @product @automatic_upgrade
18.163
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.528
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
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.037
And Tor is ready 9.392
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.928
After features/support/hooks.rb:339 0.575
After features/support/hooks.rb:108 0.000