Project Number Date
test_Tails_ISO_21565-flatpak-safe 116 02 Nov 2026, 15:40

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:29.433 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:6.942
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.639
When I start Tails from USB drive "old" with network unplugged 48.218
Then the boot device has safe access rights 2.273
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.097
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.169
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 3.657
After features/support/hooks.rb:108 0.053
Tags: @product
1:28.447
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.104
And I start Tails from USB drive "old" with network unplugged and I login 52.080
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 22.747
And I take note of which tps features are available 8.511
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 4.161
After features/support/hooks.rb:339 0.455
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.107
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.705
Then Tails is running from USB drive "old" 0.234
And all tps features are active 7.238
When I write some files expected to persist 1.315
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.877
And I take note of which tps features are available 6.685
And I shutdown Tails and wait for the computer to power off 3.815
# 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.723
After features/support/hooks.rb:339 0.248
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.309
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 without a persistent partition and stopped at Tails Greeter's login screen 8.637
And I log in to a new session 12.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.651
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.707
Then the running Tails is installed on USB drive "to_upgrade" 18.104
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.715
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.995
Then all tps features from the old Tails version are active 1.201
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 1.926
And the expected persistent files created with the old Tails version are present in the filesystem 0.970
And all persistent directories from the old Tails version have safe access rights 1.637
After features/support/hooks.rb:339 0.612
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:35.050
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.986
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.193
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.030
And Tor is ready 12.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.855
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.061
Given I shutdown Tails and wait for the computer to power off 5.467
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.685
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 7.608
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.180
When the network is plugged 0.028
And Tor is ready 10.643
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.944
Given I shutdown Tails and wait for the computer to power off 4.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.726
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.293
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.024
And Tor is ready 10.986
Then the Upgrader considers the system as up-to-date 0.158
# 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.059
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:339 0.747
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.531
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.222
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
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.046
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 8.639
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.335
After features/support/hooks.rb:339 0.750
After features/support/hooks.rb:108 0.000