Project Number Date
test_Tails_ISO_21565-flatpak-safe 51 25 Sep 2026, 03:38

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 13:7.156 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
56.872
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 12.992
When I start Tails from USB drive "old" with network unplugged 40.265
Then the boot device has safe access rights 1.868
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.617
After features/support/hooks.rb:108 0.004
Tags: @product
1:18.830
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.560
Then Tails is running from USB drive "old" 0.291
And I create a persistent partition 22.856
And I take note of which tps features are available 5.976
Then a Tails persistence partition exists on USB drive "old" 0.473
And I shutdown Tails and wait for the computer to power off 2.596
After features/support/hooks.rb:339 0.468
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.999
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.249
Then Tails is running from USB drive "old" 0.206
And all tps features are active 6.854
When I write some files expected to persist 0.983
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.581
And I take note of which tps features are available 5.615
And I shutdown Tails and wait for the computer to power off 2.520
# 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.494
After features/support/hooks.rb:339 0.266
After features/support/hooks.rb:108 0.005
Tags: @product
2:8.797
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.159
And I log in to a new session 10.287
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.553
And I plug USB drive "to_upgrade" 2.281
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.505
Then the running Tails is installed on USB drive "to_upgrade" 16.782
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.108
After features/support/hooks.rb:339 1.763
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.255
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.118
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.302
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.186
And the boot device has safe access rights 2.009
And the expected persistent files created with the old Tails version are present in the filesystem 0.999
And all persistent directories from the old Tails version have safe access rights 1.510
After features/support/hooks.rb:339 0.453
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:43.743
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 21.061
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.140
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.213
When the network is plugged 0.038
And Tor is ready 11.357
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.250
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.756
Given I shutdown Tails and wait for the computer to power off 5.166
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.851
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.007
And the file system changes introduced in version 6.2~testoverlayfs are present 0.173
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.264
When the network is plugged 0.041
And Tor is ready 10.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.845
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.243
Given I shutdown Tails and wait for the computer to power off 2.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.099
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.228
And the file system changes introduced in version 6.3~testoverlayfs are present 0.391
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.095
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.163
When the network is plugged 0.026
And Tor is ready 10.230
Then the Upgrader considers the system as up-to-date 10.422
# 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.055
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.261
After features/support/hooks.rb:339 0.636
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
2:26.657
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.727
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.024
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 9.529
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:9.096
After features/support/hooks.rb:339 0.516
After features/support/hooks.rb:108 0.000