Project Number Date
test_Tails_ISO_21565-flatpak-safe 41 20 Sep 2026, 03:23

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:46.414 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.556
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.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.903
When I start Tails from USB drive "old" with network unplugged 48.939
Then the boot device has safe access rights 2.062
And Tails is running from USB drive "old" 0.189
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.144
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.510
After features/support/hooks.rb:108 0.028
Tags: @product
1:20.321
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 "old" with network unplugged and I login 46.962
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 22.292
And I take note of which tps features are available 6.222
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 4.052
After features/support/hooks.rb:339 0.526
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.524
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.938
Then Tails is running from USB drive "old" 0.224
And all tps features are active 6.786
When I write some files expected to persist 0.981
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.248
And all persistent directories from the old Tails version have safe access rights 1.659
And I take note of which tps features are available 6.002
And I shutdown Tails and wait for the computer to power off 2.611
# 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.873
After features/support/hooks.rb:339 0.294
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.605
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.149
And I log in to a new session 11.865
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.565
And I plug USB drive "to_upgrade" 2.312
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.387
Then the running Tails is installed on USB drive "to_upgrade" 17.097
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.738
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.539
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.297
Then all tps features from the old Tails version are active 1.044
And Tails is running from USB drive "to_upgrade" 0.161
And the boot device has safe access rights 1.816
And the expected persistent files created with the old Tails version are present in the filesystem 0.821
And all persistent directories from the old Tails version have safe access rights 1.319
After features/support/hooks.rb:339 0.609
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
3:20.544
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.097
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
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.360
When the network is plugged 0.043
And Tor is ready 13.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.316
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.933
Given I shutdown Tails and wait for the computer to power off 5.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.952
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.345
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.082
# 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.186
When the network is plugged 0.025
And Tor is ready 10.048
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.464
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.339
Given I shutdown Tails and wait for the computer to power off 2.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.821
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.197
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.098
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.033
And Tor is ready 10.216
Then the Upgrader considers the system as up-to-date 0.078
# 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.115
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.274
After features/support/hooks.rb:339 0.818
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.323
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.826
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 8.297
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.853
After features/support/hooks.rb:339 0.804
After features/support/hooks.rb:108 0.000