Project Number Date
test_Tails_ISO_21565-flatpak-safe 88 14 Oct 2026, 03:25

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 10:57.671 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:19.334
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.184
When I start Tails from USB drive "old" with network unplugged 1:2.686
Then the boot device has safe access rights 1.781
And Tails is running from USB drive "old" 0.167
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.795
After features/support/hooks.rb:108 0.067
Tags: @product
1:19.613
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 47.011
Then Tails is running from USB drive "old" 0.179
And I create a persistent partition 22.212
And I take note of which tps features are available 5.626
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 3.991
After features/support/hooks.rb:339 0.213
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.832
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.203
Then Tails is running from USB drive "old" 0.209
And all tps features are active 6.845
When I write some files expected to persist 1.143
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.203
And all persistent directories from the old Tails version have safe access rights 1.458
And I take note of which tps features are available 5.675
And I shutdown Tails and wait for the computer to power off 2.527
# 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.311
After features/support/hooks.rb:339 0.437
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.962
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.103
And I log in to a new session 12.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.584
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.450
Then the running Tails is installed on USB drive "to_upgrade" 17.836
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.782
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.154
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.729
Then all tps features from the old Tails version are active 1.115
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 1.879
And the expected persistent files created with the old Tails version are present in the filesystem 0.847
And all persistent directories from the old Tails version have safe access rights 1.231
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.051
Tags: @product @automatic_upgrade
3:18.336
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 7.886
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.227
When the network is plugged 0.034
And Tor is ready 11.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.914
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.051
Given I shutdown Tails and wait for the computer to power off 5.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.458
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.422
And the file system changes introduced in version 6.2~testoverlayfs are present 0.150
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.099
# 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.177
When the network is plugged 0.035
And Tor is ready 11.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.306
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.454
Given I shutdown Tails and wait for the computer to power off 2.561
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.646
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 6.986
And the file system changes introduced in version 6.3~testoverlayfs are present 0.264
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.093
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.030
And Tor is ready 10.088
Then the Upgrader considers the system as up-to-date 0.073
# 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.096
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 0.980
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
17.438
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.613
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
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.039
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.055
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.450
After features/support/hooks.rb:339 0.712
After features/support/hooks.rb:108 0.000