Project Number Date
test_Tails_ISO_stable 6180 02 Mar 2026, 08:04

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 13:50.419 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:50.580
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.332
When I start Tails from USB drive "old" with network unplugged 1:32.828
Then the boot device has safe access rights 2.684
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.165
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 1.653
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.945
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 55.292
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 23.015
And I take note of which tps features are available 0.643
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 8.161
After features/support/hooks.rb:331 0.397
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.808
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.274
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.020
When I write some files expected to persist 1.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.451
And all persistent directories from the old Tails version have safe access rights 1.789
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.170
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.040
After features/support/hooks.rb:331 0.576
After features/support/hooks.rb:100 0.006
Tags: @product
2:47.687
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.070
And I log in to a new session 24.740
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.764
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:56.389
Then the running Tails is installed on USB drive "to_upgrade" 15.179
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 4.417
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.096
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.486
Then all tps features from the old Tails version are active 0.913
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 2.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.185
And all persistent directories from the old Tails version have safe access rights 1.853
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.073
4:44.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.478
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.352
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.081
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.018
And Tor is ready 23.404
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.176
Given I shutdown Tails and wait for the computer to power off 26.769
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.766
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.028
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.220
When the network is plugged 0.019
And Tor is ready 22.284
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.055
Given I shutdown Tails and wait for the computer to power off 17.059
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.488
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.100
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.019
And Tor is ready 20.762
Then the Upgrader considers the system as up-to-date 0.140
# 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.886
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 0.995
After features/support/hooks.rb:100 0.010
27.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.569
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 18.843
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.376
After features/support/hooks.rb:331 0.692
After features/support/hooks.rb:100 0.000