Project Number Date
test_Tails_ISO_21565-flatpak-safe 11 26 Aug 2026, 03:17

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:3.653 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:16.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.200
When I start Tails from USB drive "old" with network unplugged 59.853
Then the boot device has safe access rights 1.941
And Tails is running from USB drive "old" 0.164
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.146
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 1.726
After features/support/hooks.rb:108 0.004
Tags: @product
1:18.198
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.098
Then Tails is running from USB drive "old" 0.193
And I create a persistent partition 22.699
And I take note of which tps features are available 6.110
Then a Tails persistence partition exists on USB drive "old" 0.476
And I shutdown Tails and wait for the computer to power off 2.548
After features/support/hooks.rb:339 0.109
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.539
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.865
Then Tails is running from USB drive "old" 0.190
And all tps features are active 6.785
When I write some files expected to persist 1.012
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.225
And all persistent directories from the old Tails version have safe access rights 1.638
And I take note of which tps features are available 5.988
And I shutdown Tails and wait for the computer to power off 2.504
# 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.103
After features/support/hooks.rb:339 0.273
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.792
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.020
And I log in to a new session 12.097
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.735
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.559
Then the running Tails is installed on USB drive "to_upgrade" 16.907
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.930
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.756
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.104
Then all tps features from the old Tails version are active 0.991
And Tails is running from USB drive "to_upgrade" 0.176
And the boot device has safe access rights 1.929
And the expected persistent files created with the old Tails version are present in the filesystem 0.885
And all persistent directories from the old Tails version have safe access rights 1.588
After features/support/hooks.rb:339 0.873
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:25.755
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 8.067
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.174
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.266
When the network is plugged 0.027
And Tor is ready 12.884
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.971
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.707
Given I shutdown Tails and wait for the computer to power off 5.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.873
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.431
And the file system changes introduced in version 6.2~testoverlayfs are present 0.158
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.191
When the network is plugged 0.025
And Tor is ready 10.091
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.373
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.573
Given I shutdown Tails and wait for the computer to power off 3.996
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.271
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.299
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.102
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.028
And Tor is ready 10.113
Then the Upgrader considers the system as up-to-date 0.143
# 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.157
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:339 0.568
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.991
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.457
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.173
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.833
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.386
After features/support/hooks.rb:339 0.678
After features/support/hooks.rb:108 0.000