Project Number Date
test_Tails_ISO_stable-flatpak 22 19 Sep 2026, 19:41

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:9.544 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:1.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.262
When I start Tails from USB drive "old" with network unplugged 45.015
Then the boot device has safe access rights 1.804
And Tails is running from USB drive "old" 0.174
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.028
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.817
After features/support/hooks.rb:108 0.005
Tags: @product
1:22.214
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 47.607
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 23.296
And I take note of which tps features are available 6.415
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 4.082
After features/support/hooks.rb:339 0.093
After features/support/hooks.rb:108 0.005
Tags: @product
1:30.397
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.837
Then Tails is running from USB drive "old" 0.177
And all tps features are active 6.798
When I write some files expected to persist 1.246
# 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.262
And all persistent directories from the old Tails version have safe access rights 1.830
And I take note of which tps features are available 6.360
And I shutdown Tails and wait for the computer to power off 2.517
# 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.120
After features/support/hooks.rb:339 0.408
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.924
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.322
And I log in to a new session 11.757
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.871
And I plug USB drive "to_upgrade" 2.178
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.132
Then the running Tails is installed on USB drive "to_upgrade" 17.424
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.572
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.723
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.026
Then all tps features from the old Tails version are active 0.999
And Tails is running from USB drive "to_upgrade" 0.166
And the boot device has safe access rights 1.811
And the expected persistent files created with the old Tails version are present in the filesystem 1.035
And all persistent directories from the old Tails version have safe access rights 1.600
After features/support/hooks.rb:339 0.927
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.827
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.053
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.280
When the network is plugged 0.038
And Tor is ready 13.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.659
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.029
Given I shutdown Tails and wait for the computer to power off 6.740
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.612
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 7.370
And the file system changes introduced in version 6.2~testoverlayfs are present 0.148
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.089
# 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.184
When the network is plugged 0.034
And Tor is ready 10.308
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.594
Given I shutdown Tails and wait for the computer to power off 2.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.746
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.543
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.050
# 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.138
When the network is plugged 0.024
And Tor is ready 10.239
Then the Upgrader considers the system as up-to-date 10.388
# 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.006
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 1.079
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.750
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.635
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.050
And Tor is ready 9.817
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.992
After features/support/hooks.rb:339 0.990
After features/support/hooks.rb:108 0.000