Project Number Date
test_Tails_ISO_21565-flatpak-safe 50 24 Sep 2026, 14:52

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 19:38.226 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:10.687
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.018
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.196
When I start Tails from USB drive "old" with network unplugged 53.894
Then the boot device has safe access rights 1.971
And Tails is running from USB drive "old" 0.171
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 3.405
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.725
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.904
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 23.569
And I take note of which tps features are available 6.636
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 3.810
After features/support/hooks.rb:339 0.096
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.736
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 1:0.695
Then Tails is running from USB drive "old" 0.180
And all tps features are active 7.541
When I write some files expected to persist 1.145
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.725
And I take note of which tps features are available 5.774
And I shutdown Tails and wait for the computer to power off 2.506
# 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.653
After features/support/hooks.rb:339 0.635
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.304
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.319
And I log in to a new session 12.405
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.674
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.598
Then the running Tails is installed on USB drive "to_upgrade" 17.797
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.102
After features/support/hooks.rb:339 1.735
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.532
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
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.196
Then all tps features from the old Tails version are active 1.235
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 2.301
And the expected persistent files created with the old Tails version are present in the filesystem 0.882
And all persistent directories from the old Tails version have safe access rights 1.605
After features/support/hooks.rb:339 0.679
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
9:45.523
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.407
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.326
When the network is plugged 0.024
And Tor is ready 12.689
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4:2.980
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.388
Given I shutdown Tails and wait for the computer to power off 5.356
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.317
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.521
And the file system changes introduced in version 6.2~testoverlayfs are present 0.170
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.150
When the network is plugged 0.035
And Tor is ready 10.301
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2:5.903
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.612
Given I shutdown Tails and wait for the computer to power off 3.853
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.151
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.686
And the file system changes introduced in version 6.3~testoverlayfs are present 0.292
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.092
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.033
And Tor is ready 10.784
Then the Upgrader considers the system as up-to-date 10.419
# 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.608
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:339 1.017
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
2:24.715
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.599
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.730
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:6.026
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.000