Project Number Date
test_Tails_ISO_21559-flatpak-locale-tests 2 01 Sep 2026, 19:14

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 12:23.877 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:18.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.096
And I write an old version of the Tails USB image to disk "old" 13.937
When I start Tails from USB drive "old" with network unplugged 1:0.248
Then the boot device has safe access rights 2.724
And Tails is running from USB drive "old" 0.230
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.187
After features/support/hooks.rb:108 0.007
Tags: @product
1:33.494
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 52.335
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 26.262
And I take note of which tps features are available 9.839
Then a Tails persistence partition exists on USB drive "old" 0.569
And I shutdown Tails and wait for the computer to power off 4.108
After features/support/hooks.rb:339 0.366
After features/support/hooks.rb:108 0.007
Tags: @product
1:43.538
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.286
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.612
Then Tails is running from USB drive "old" 0.271
And all tps features are active 9.583
When I write some files expected to persist 1.092
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.594
And I take note of which tps features are available 6.598
And I shutdown Tails and wait for the computer to power off 4.028
# 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" 12.052
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.005
Tags: @product
2:18.985
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 9.350
And I log in to a new session 12.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.284
And I plug USB drive "to_upgrade" 2.262
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.537
Then the running Tails is installed on USB drive "to_upgrade" 19.598
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.971
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.835
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.993
Then all tps features from the old Tails version are active 1.195
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.392
And the expected persistent files created with the old Tails version are present in the filesystem 1.156
And all persistent directories from the old Tails version have safe access rights 1.763
After features/support/hooks.rb:339 0.827
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:55.187
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.364
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.286
When the network is plugged 0.024
And Tor is ready 13.091
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.003
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.978
Given I shutdown Tails and wait for the computer to power off 5.432
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.948
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.938
And the file system changes introduced in version 6.2~testoverlayfs are present 0.224
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.127
# 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.191
When the network is plugged 0.040
And Tor is ready 10.183
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.660
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.416
Given I shutdown Tails and wait for the computer to power off 2.682
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.323
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.282
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.400
When the network is plugged 0.024
And Tor is ready 10.840
Then the Upgrader considers the system as up-to-date 10.692
# 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 4.384
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.481
After features/support/hooks.rb:339 0.794
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
21.083
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.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
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.060
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.548
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.903
After features/support/hooks.rb:339 0.614
After features/support/hooks.rb:108 0.000