Project Number Date
test_Tails_ISO_21565-flatpak-safe 23 02 Sep 2026, 03:25

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:8.771 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:17.483
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.125
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.771
When I start Tails from USB drive "old" with network unplugged 1:1.196
Then the boot device has safe access rights 1.748
And Tails is running from USB drive "old" 0.177
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.213
And I unplug USB drive "old" 0.104
After features/support/hooks.rb:339 3.649
After features/support/hooks.rb:108 0.067
Tags: @product
1:17.998
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.748
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 22.106
And I take note of which tps features are available 5.710
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 2.630
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.825
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.451
Then Tails is running from USB drive "old" 0.167
And all tps features are active 7.051
When I write some files expected to persist 1.027
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.269
And all persistent directories from the old Tails version have safe access rights 1.531
And I take note of which tps features are available 5.295
And I shutdown Tails and wait for the computer to power off 2.599
# 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.192
After features/support/hooks.rb:339 0.451
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.547
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.149
And I log in to a new session 12.817
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.550
And I plug USB drive "to_upgrade" 2.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.570
Then the running Tails is installed on USB drive "to_upgrade" 18.021
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 2.029
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.086
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.519
Then all tps features from the old Tails version are active 0.974
And Tails is running from USB drive "to_upgrade" 0.167
And the boot device has safe access rights 2.083
And the expected persistent files created with the old Tails version are present in the filesystem 0.890
And all persistent directories from the old Tails version have safe access rights 1.357
After features/support/hooks.rb:339 0.557
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
3:29.118
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.838
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.198
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.039
And Tor is ready 13.038
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.877
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.661
Given I shutdown Tails and wait for the computer to power off 5.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.824
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 7.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.157
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.083
# 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.149
When the network is plugged 0.042
And Tor is ready 10.116
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.820
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.472
Given I shutdown Tails and wait for the computer to power off 2.533
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.677
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.268
And only the 6.3~testoverlayfs SquashFS delta is installed 0.026
# 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.110
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.150
When the network is plugged 0.037
And Tor is ready 9.928
Then the Upgrader considers the system as up-to-date 10.374
# 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.077
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.309
After features/support/hooks.rb:339 0.716
After features/support/hooks.rb:108 0.064
Tags: @product @automatic_upgrade
19.711
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.910
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.588
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.888
After features/support/hooks.rb:339 1.084
After features/support/hooks.rb:108 0.000