Project Number Date
test_Tails_ISO_stable 6725 06 Oct 2026, 11:55

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:17.033 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:9.336
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.121
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.872
When I start Tails from USB drive "old" with network unplugged 50.607
Then the boot device has safe access rights 2.037
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 3.716
After features/support/hooks.rb:108 0.005
Tags: @product
1:20.220
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 47.362
Then Tails is running from USB drive "old" 0.160
And I create a persistent partition 22.172
And I take note of which tps features are available 5.975
Then a Tails persistence partition exists on USB drive "old" 0.442
And I shutdown Tails and wait for the computer to power off 4.009
After features/support/hooks.rb:339 0.156
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.821
Then Tails is running from USB drive "old" 0.184
And all tps features are active 6.053
When I write some files expected to persist 0.995
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.139
And all persistence configuration files have safe access rights 0.259
And all persistent directories from the old Tails version have safe access rights 1.554
And I take note of which tps features are available 6.170
And I shutdown Tails and wait for the computer to power off 4.034
# 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.622
After features/support/hooks.rb:339 0.441
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.821
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.603
And I log in to a new session 10.197
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.452
Then the running Tails is installed on USB drive "to_upgrade" 18.297
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.115
After features/support/hooks.rb:339 1.604
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.824
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.544
Then all tps features from the old Tails version are active 1.391
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 1.989
And the expected persistent files created with the old Tails version are present in the filesystem 0.992
And all persistent directories from the old Tails version have safe access rights 1.608
After features/support/hooks.rb:339 0.893
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:36.761
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.247
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.192
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.033
And Tor is ready 13.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.330
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.340
Given I shutdown Tails and wait for the computer to power off 6.634
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.620
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 7.315
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.033
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.175
When the network is plugged 0.028
And Tor is ready 10.396
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.584
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.515
Given I shutdown Tails and wait for the computer to power off 2.614
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.433
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.170
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.038
And Tor is ready 10.364
Then the Upgrader considers the system as up-to-date 0.184
# 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.612
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.465
After features/support/hooks.rb:339 1.380
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.166
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.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 8.430
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.678
After features/support/hooks.rb:339 1.023
After features/support/hooks.rb:108 0.000