Project Number Date
test_Tails_ISO_21565-flatpak-safe 136 12 Nov 2026, 03:25

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:43.306 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:3.317
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.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.369
When I start Tails from USB drive "old" with network unplugged 46.497
Then the boot device has safe access rights 1.881
And Tails is running from USB drive "old" 0.159
And there is no persistence partition on USB drive "old" 0.034
And process "udev-watchdog" is running 0.024
And udev-watchdog is monitoring the correct device 0.135
And I unplug USB drive "old" 0.103
After features/support/hooks.rb:339 1.613
After features/support/hooks.rb:108 0.004
Tags: @product
1:19.639
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 46.696
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 22.034
And I take note of which tps features are available 6.184
Then a Tails persistence partition exists on USB drive "old" 0.479
And I shutdown Tails and wait for the computer to power off 3.963
After features/support/hooks.rb:339 0.212
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.505
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.237
Then Tails is running from USB drive "old" 0.202
And all tps features are active 6.970
When I write some files expected to persist 0.911
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.137
And all persistence configuration files have safe access rights 0.244
And all persistent directories from the old Tails version have safe access rights 1.397
And I take note of which tps features are available 5.462
And I shutdown Tails and wait for the computer to power off 2.503
# 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.364
After features/support/hooks.rb:339 0.299
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.666
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.147
And I log in to a new session 10.633
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.684
And I plug USB drive "to_upgrade" 2.173
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.636
Then the running Tails is installed on USB drive "to_upgrade" 17.186
And I unplug USB drive "to_upgrade" 0.106
And I unplug USB drive "__internal" 0.099
After features/support/hooks.rb:339 1.591
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.087
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.067
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.645
Then all tps features from the old Tails version are active 1.063
And Tails is running from USB drive "to_upgrade" 0.159
And the boot device has safe access rights 1.963
And the expected persistent files created with the old Tails version are present in the filesystem 0.854
And all persistent directories from the old Tails version have safe access rights 1.333
After features/support/hooks.rb:339 0.647
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
3:20.710
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.018
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.285
When the network is plugged 0.030
And Tor is ready 11.999
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.916
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.126
Given I shutdown Tails and wait for the computer to power off 5.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.208
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.027
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.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.104
# 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.152
When the network is plugged 0.022
And Tor is ready 9.992
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.343
Given I shutdown Tails and wait for the computer to power off 4.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.163
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.626
And the file system changes introduced in version 6.3~testoverlayfs are present 0.294
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.177
When the network is plugged 0.032
And Tor is ready 9.904
Then the Upgrader considers the system as up-to-date 0.110
# 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.164
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.310
After features/support/hooks.rb:339 0.530
After features/support/hooks.rb:108 0.064
Tags: @product @automatic_upgrade
18.378
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.673
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.101
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.303
After features/support/hooks.rb:339 0.777
After features/support/hooks.rb:108 0.000