Project Number Date
test_Tails_ISO_devel 4657 05 Oct 2026, 11: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:36.154 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
59.072
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.855
When I start Tails from USB drive "old" with network unplugged 40.948
Then the boot device has safe access rights 2.459
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.166
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 3.597
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.665
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 "old" with network unplugged and I login 49.408
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 24.727
And I take note of which tps features are available 6.659
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 3.999
After features/support/hooks.rb:339 0.177
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.814
Then Tails is running from USB drive "old" 0.207
And all tps features are active 7.528
When I write some files expected to persist 1.254
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.152
And all persistence configuration files have safe access rights 0.211
And all persistent directories from the old Tails version have safe access rights 1.691
And I take note of which tps features are available 6.211
And I shutdown Tails and wait for the computer to power off 2.596
# 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.839
After features/support/hooks.rb:339 0.191
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.862
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.360
And I log in to a new session 12.491
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.677
And I plug USB drive "to_upgrade" 2.428
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.074
Then the running Tails is installed on USB drive "to_upgrade" 18.543
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 1.799
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.721
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.732
Then all tps features from the old Tails version are active 0.995
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.184
And the expected persistent files created with the old Tails version are present in the filesystem 0.916
And all persistent directories from the old Tails version have safe access rights 1.616
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
3:55.359
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 35.003
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.031
And Tor is ready 12.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.947
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.506
Given I shutdown Tails and wait for the computer to power off 5.337
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.218
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.519
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.087
# 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.033
And Tor is ready 10.767
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.343
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.821
Given I shutdown Tails and wait for the computer to power off 2.623
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.980
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.568
And the file system changes introduced in version 6.3~testoverlayfs are present 0.576
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.162
When the network is plugged 0.042
And Tor is ready 10.501
Then the Upgrader considers the system as up-to-date 0.102
# 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.137
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
17.853
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.919
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
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.038
And Tor is ready 8.205
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.417
After features/support/hooks.rb:339 0.828
After features/support/hooks.rb:108 0.000