Project Number Date
test_Tails_ISO_21565-flatpak-safe 27 06 Sep 2026, 03:16

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:7.015 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:0.341
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.283
When I start Tails from USB drive "old" with network unplugged 43.351
Then the boot device has safe access rights 2.131
And Tails is running from USB drive "old" 0.151
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.122
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 1.758
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.241
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.121
And I start Tails from USB drive "old" with network unplugged and I login 45.331
Then Tails is running from USB drive "old" 0.220
And I create a persistent partition 22.334
And I take note of which tps features are available 6.037
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 2.692
After features/support/hooks.rb:339 0.625
After features/support/hooks.rb:108 0.014
Tags: @product
1:26.675
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.095
Then Tails is running from USB drive "old" 0.198
And all tps features are active 7.058
When I write some files expected to persist 1.109
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.497
And I take note of which tps features are available 5.450
And I shutdown Tails and wait for the computer to power off 2.525
# 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.155
After features/support/hooks.rb:339 0.128
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.177
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.094
And I log in to a new session 11.917
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.633
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.572
Then the running Tails is installed on USB drive "to_upgrade" 17.498
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:339 1.942
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.590
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.980
Then all tps features from the old Tails version are active 1.076
And Tails is running from USB drive "to_upgrade" 0.131
And the boot device has safe access rights 2.016
And the expected persistent files created with the old Tails version are present in the filesystem 0.848
And all persistent directories from the old Tails version have safe access rights 1.457
After features/support/hooks.rb:339 0.605
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
3:47.051
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 21.008
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.180
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.209
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.223
When the network is plugged 0.033
And Tor is ready 12.933
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.317
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.861
Given I shutdown Tails and wait for the computer to power off 6.416
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.691
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.612
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.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.084
# 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.142
When the network is plugged 0.022
And Tor is ready 10.187
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.877
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.938
Given I shutdown Tails and wait for the computer to power off 4.046
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.952
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.873
And the file system changes introduced in version 6.3~testoverlayfs are present 0.205
And only the 6.3~testoverlayfs SquashFS delta is installed 0.032
# 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.147
When the network is plugged 0.039
And Tor is ready 9.921
Then the Upgrader considers the system as up-to-date 10.409
# 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 2.943
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.323
After features/support/hooks.rb:339 0.811
After features/support/hooks.rb:108 0.027
Tags: @product @automatic_upgrade
18.937
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.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.519
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.325
After features/support/hooks.rb:339 0.768
After features/support/hooks.rb:108 0.000