Project Number Date
test_Tails_ISO_21565-flatpak-safe 8 23 Aug 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 10:59.816 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:9.363
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.730
When I start Tails from USB drive "old" with network unplugged 53.048
Then the boot device has safe access rights 1.956
And Tails is running from USB drive "old" 0.185
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.150
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.639
After features/support/hooks.rb:108 0.005
Tags: @product
1:18.376
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.679
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 22.121
And I take note of which tps features are available 6.220
Then a Tails persistence partition exists on USB drive "old" 0.543
And I shutdown Tails and wait for the computer to power off 2.535
After features/support/hooks.rb:339 0.447
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.663
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.467
Then Tails is running from USB drive "old" 0.175
And all tps features are active 6.614
When I write some files expected to persist 0.976
# 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.204
And all persistent directories from the old Tails version have safe access rights 1.700
And I take note of which tps features are available 5.889
And I shutdown Tails and wait for the computer to power off 2.492
# 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" 10.919
After features/support/hooks.rb:339 0.137
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.306
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.284
And I log in to a new session 9.992
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.537
And I plug USB drive "to_upgrade" 2.167
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.638
Then the running Tails is installed on USB drive "to_upgrade" 17.416
And I unplug USB drive "to_upgrade" 0.114
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 1.795
After features/support/hooks.rb:108 0.000
Tags: @product
1:2.730
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.315
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.258
And the boot device has safe access rights 1.997
And the expected persistent files created with the old Tails version are present in the filesystem 0.784
And all persistent directories from the old Tails version have safe access rights 1.284
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:34.039
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.708
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.169
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.262
When the network is plugged 0.033
And Tor is ready 11.253
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.904
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.730
Given I shutdown Tails and wait for the computer to power off 5.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.862
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.168
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.114
# 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.153
When the network is plugged 0.023
And Tor is ready 9.944
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.553
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.489
Given I shutdown Tails and wait for the computer to power off 3.921
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.165
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 7.157
And the file system changes introduced in version 6.3~testoverlayfs are present 0.286
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.081
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.028
And Tor is ready 10.156
Then the Upgrader considers the system as up-to-date 0.067
# 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.144
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.360
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.056
Tags: @product @automatic_upgrade
19.336
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.738
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.356
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.954
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.000