Project Number Date
test_Tails_ISO_21565-flatpak-safe 70 05 Oct 2026, 19: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 11:53.585 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:16.288
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.149
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 14.422
When I start Tails from USB drive "old" with network unplugged 56.754
Then the boot device has safe access rights 3.139
And Tails is running from USB drive "old" 0.244
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 1.331
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.131
And I start Tails from USB drive "old" with network unplugged and I login 50.859
Then Tails is running from USB drive "old" 0.209
And I create a persistent partition 23.470
And I take note of which tps features are available 6.862
Then a Tails persistence partition exists on USB drive "old" 0.536
And I shutdown Tails and wait for the computer to power off 3.823
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.908
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.094
Then Tails is running from USB drive "old" 0.229
And all tps features are active 7.468
When I write some files expected to persist 1.132
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.351
And all persistent directories from the old Tails version have safe access rights 1.701
And I take note of which tps features are available 6.532
And I shutdown Tails and wait for the computer to power off 2.519
# 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.561
After features/support/hooks.rb:339 0.463
After features/support/hooks.rb:108 0.006
Tags: @product
2:28.472
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 without a persistent partition and stopped at Tails Greeter's login screen 22.823
And I log in to a new session 12.122
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.236
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.007
Then the running Tails is installed on USB drive "to_upgrade" 18.573
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 2.007
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.875
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.735
Then all tps features from the old Tails version are active 1.376
And Tails is running from USB drive "to_upgrade" 0.295
And the boot device has safe access rights 2.379
And the expected persistent files created with the old Tails version are present in the filesystem 1.074
And all persistent directories from the old Tails version have safe access rights 1.927
After features/support/hooks.rb:339 1.058
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:36.324
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 8.238
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.036
And Tor is ready 13.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.155
Given I shutdown Tails and wait for the computer to power off 5.324
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.617
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.801
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.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.186
# 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.295
When the network is plugged 0.026
And Tor is ready 11.041
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.048
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.200
Given I shutdown Tails and wait for the computer to power off 4.042
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.095
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.476
And the file system changes introduced in version 6.3~testoverlayfs are present 0.286
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.094
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.024
And Tor is ready 10.483
Then the Upgrader considers the system as up-to-date 0.095
# 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.352
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 0.975
After features/support/hooks.rb:108 0.047
Tags: @product @automatic_upgrade
18.822
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 8.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.831
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.339
After features/support/hooks.rb:339 0.851
After features/support/hooks.rb:108 0.000