Project Number Date
test_Tails_ISO_stable-flatpak 45 13 Oct 2026, 20:18

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:20.735 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:5.882
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
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 48.959
Then the boot device has safe access rights 1.964
And Tails is running from USB drive "old" 0.194
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.134
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.675
After features/support/hooks.rb:108 0.006
Tags: @product
1:23.776
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 48.381
Then Tails is running from USB drive "old" 0.151
And I create a persistent partition 24.490
And I take note of which tps features are available 6.162
Then a Tails persistence partition exists on USB drive "old" 0.480
And I shutdown Tails and wait for the computer to power off 4.030
After features/support/hooks.rb:339 0.563
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.356
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.897
Then Tails is running from USB drive "old" 0.262
And all tps features are active 7.820
When I write some files expected to persist 1.440
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.103
And all persistence configuration files have safe access rights 0.250
And all persistent directories from the old Tails version have safe access rights 1.972
And I take note of which tps features are available 5.928
And I shutdown Tails and wait for the computer to power off 3.995
# 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.594
After features/support/hooks.rb:339 0.450
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.916
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 without a persistent partition and stopped at Tails Greeter's login screen 8.328
And I log in to a new session 12.274
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.777
And I plug USB drive "to_upgrade" 2.345
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.616
Then the running Tails is installed on USB drive "to_upgrade" 18.310
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 1.818
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.754
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.490
Then all tps features from the old Tails version are active 1.073
And Tails is running from USB drive "to_upgrade" 0.153
And the boot device has safe access rights 1.913
And the expected persistent files created with the old Tails version are present in the filesystem 1.133
And all persistent directories from the old Tails version have safe access rights 1.902
After features/support/hooks.rb:339 0.890
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:34.796
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 8.302
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.035
And Tor is ready 12.984
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.140
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.591
Given I shutdown Tails and wait for the computer to power off 5.265
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.064
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.337
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.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.096
# 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.166
When the network is plugged 0.023
And Tor is ready 10.609
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.318
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.903
Given I shutdown Tails and wait for the computer to power off 4.117
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.657
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.019
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.035
And Tor is ready 10.242
Then the Upgrader considers the system as up-to-date 0.098
# 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.646
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.488
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.252
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.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.023
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.929
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.000