Project Number Date
test_Tails_ISO_21565-flatpak-safe 100 26 Oct 2026, 03:36

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:36.685 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:15.842
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.634
When I start Tails from USB drive "old" with network unplugged 58.319
Then the boot device has safe access rights 2.103
And Tails is running from USB drive "old" 0.215
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.184
After features/support/hooks.rb:108 0.007
Tags: @product
1:24.802
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.151
And I start Tails from USB drive "old" with network unplugged and I login 49.409
Then Tails is running from USB drive "old" 0.191
And I create a persistent partition 23.622
And I take note of which tps features are available 6.807
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 4.003
After features/support/hooks.rb:339 0.593
After features/support/hooks.rb:108 0.009
Tags: @product
1:35.896
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.167
Then Tails is running from USB drive "old" 0.301
And all tps features are active 7.439
When I write some files expected to persist 1.161
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 1.881
And I take note of which tps features are available 6.451
And I shutdown Tails and wait for the computer to power off 2.630
# 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.288
After features/support/hooks.rb:339 0.456
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.947
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 without a persistent partition and stopped at Tails Greeter's login screen 8.672
And I log in to a new session 12.214
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.775
And I plug USB drive "to_upgrade" 2.365
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.736
Then the running Tails is installed on USB drive "to_upgrade" 18.950
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 3.665
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.024
Then all tps features from the old Tails version are active 1.434
And Tails is running from USB drive "to_upgrade" 0.176
And the boot device has safe access rights 2.438
And the expected persistent files created with the old Tails version are present in the filesystem 0.959
And all persistent directories from the old Tails version have safe access rights 1.765
After features/support/hooks.rb:339 0.809
After features/support/hooks.rb:108 0.092
Tags: @product @automatic_upgrade
3:35.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.394
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.102
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.397
When the network is plugged 0.031
And Tor is ready 14.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.133
Given I shutdown Tails and wait for the computer to power off 5.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.954
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.248
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.159
When the network is plugged 0.034
And Tor is ready 10.778
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.326
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.827
Given I shutdown Tails and wait for the computer to power off 2.581
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.195
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.376
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.032
And Tor is ready 10.144
Then the Upgrader considers the system as up-to-date 0.096
# 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.729
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 1.082
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
19.454
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.134
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 10.633
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.319
After features/support/hooks.rb:339 0.744
After features/support/hooks.rb:108 0.000