Project Number Date
test_Tails_ISO_stable 6227 24 Mar 2026, 12: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 12:32.353 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:12.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 14.093
When I start Tails from USB drive "old" with network unplugged 53.943
Then the boot device has safe access rights 2.921
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 1.278
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 54.609
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 25.022
And I take note of which tps features are available 0.843
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 2.704
After features/support/hooks.rb:331 0.272
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.191
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.550
Then Tails is running from USB drive "old" 0.242
And all tps features are active 1.171
When I write some files expected to persist 1.442
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 1.859
And I take note of which tps features are available 0.231
And I shutdown Tails and wait for the computer to power off 8.520
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.503
After features/support/hooks.rb:331 0.177
After features/support/hooks.rb:100 0.007
Tags: @product
2:14.870
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.801
And I log in to a new session 13.275
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.090
And I plug USB drive "to_upgrade" 2.253
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.121
Then the running Tails is installed on USB drive "to_upgrade" 17.053
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 2.282
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.335
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.113
Then all tps features from the old Tails version are active 1.842
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.684
And the expected persistent files created with the old Tails version are present in the filesystem 1.348
And all persistent directories from the old Tails version have safe access rights 2.004
After features/support/hooks.rb:331 0.896
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:32.685
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.234
And no SquashFS delta is installed 0.089
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
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.300
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.023
And Tor is ready 19.737
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.488
Given I shutdown Tails and wait for the computer to power off 14.664
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.824
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.096
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.217
When the network is plugged 0.018
And Tor is ready 20.613
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.454
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.660
Given I shutdown Tails and wait for the computer to power off 17.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.768
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.072
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.053
And Tor is ready 20.447
Then the Upgrader considers the system as up-to-date 0.100
# 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 4.324
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.417
After features/support/hooks.rb:331 0.919
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.409
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 8.042
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.018
And Tor is ready 17.616
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.361
After features/support/hooks.rb:331 0.816
After features/support/hooks.rb:100 0.000