Project Number Date
test_Tails_ISO_21565-flatpak-safe 102 26 Oct 2026, 21:50

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:47.749 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.637
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.607
When I start Tails from USB drive "old" with network unplugged 51.588
Then the boot device has safe access rights 2.505
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.248
After features/support/hooks.rb:339 3.458
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.142
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 50.235
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 25.013
And I take note of which tps features are available 8.520
Then a Tails persistence partition exists on USB drive "old" 0.609
And I shutdown Tails and wait for the computer to power off 4.392
After features/support/hooks.rb:339 0.218
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.183
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.273
Then Tails is running from USB drive "old" 0.205
And all tps features are active 8.663
When I write some files expected to persist 1.366
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.262
And all persistent directories from the old Tails version have safe access rights 1.604
And I take note of which tps features are available 7.498
And I shutdown Tails and wait for the computer to power off 4.122
# 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.883
After features/support/hooks.rb:339 0.154
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.966
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.415
And I log in to a new session 12.061
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.666
And I plug USB drive "to_upgrade" 2.515
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.694
Then the running Tails is installed on USB drive "to_upgrade" 19.377
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.907
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.950
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.031
Then all tps features from the old Tails version are active 1.110
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.451
And the expected persistent files created with the old Tails version are present in the filesystem 1.015
And all persistent directories from the old Tails version have safe access rights 2.033
After features/support/hooks.rb:339 0.702
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:41.444
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.444
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.028
And Tor is ready 14.161
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.987
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.773
Given I shutdown Tails and wait for the computer to power off 5.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.397
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.477
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.097
# 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.158
When the network is plugged 0.027
And Tor is ready 10.779
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 4.374
Given I shutdown Tails and wait for the computer to power off 3.944
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.130
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.829
And the file system changes introduced in version 6.3~testoverlayfs are present 0.412
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.201
When the network is plugged 0.025
And Tor is ready 10.573
Then the Upgrader considers the system as up-to-date 0.103
# 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.061
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.467
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
20.423
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.619
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.032
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.677
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.815
After features/support/hooks.rb:339 0.817
After features/support/hooks.rb:108 0.000