Project Number Date
test_Tails_ISO_21565-flatpak-safe 92 18 Oct 2026, 03:22

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:14.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:16.091
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 12.849
When I start Tails from USB drive "old" with network unplugged 59.623
Then the boot device has safe access rights 1.956
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.422
After features/support/hooks.rb:108 0.054
Tags: @product
1:21.468
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 "old" with network unplugged and I login 47.745
Then Tails is running from USB drive "old" 0.190
And I create a persistent partition 22.068
And I take note of which tps features are available 5.657
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 5.231
After features/support/hooks.rb:339 0.362
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.802
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.081
Then Tails is running from USB drive "old" 0.272
And all tps features are active 6.985
When I write some files expected to persist 0.973
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.102
And all persistence configuration files have safe access rights 0.179
And all persistent directories from the old Tails version have safe access rights 1.427
And I take note of which tps features are available 6.017
And I shutdown Tails and wait for the computer to power off 2.537
# 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.117
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.869
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.229
And I log in to a new session 10.808
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.711
And I plug USB drive "to_upgrade" 2.197
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.738
Then the running Tails is installed on USB drive "to_upgrade" 17.942
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.864
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.424
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.136
Then all tps features from the old Tails version are active 1.089
And Tails is running from USB drive "to_upgrade" 0.183
And the boot device has safe access rights 1.782
And the expected persistent files created with the old Tails version are present in the filesystem 0.863
And all persistent directories from the old Tails version have safe access rights 1.300
After features/support/hooks.rb:339 0.794
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:33.093
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 20.813
And no SquashFS delta is installed 0.046
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.285
When the network is plugged 0.042
And Tor is ready 13.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.854
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.986
Given I shutdown Tails and wait for the computer to power off 4.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.792
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.359
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.094
# 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.196
When the network is plugged 0.024
And Tor is ready 10.191
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.310
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.788
Given I shutdown Tails and wait for the computer to power off 3.954
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.019
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.212
And the file system changes introduced in version 6.3~testoverlayfs are present 0.297
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.071
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.164
When the network is plugged 0.021
And Tor is ready 10.240
Then the Upgrader considers the system as up-to-date 0.117
# 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.120
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.291
After features/support/hooks.rb:339 0.664
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.475
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.485
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 8.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.467
After features/support/hooks.rb:339 0.657
After features/support/hooks.rb:108 0.000