Project Number Date
test_Tails_ISO_stable 6386 19 May 2026, 14: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 11:54.096 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:11.075
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.397
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.418
When I start Tails from USB drive "old" with network unplugged 50.877
Then the boot device has safe access rights 3.419
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.122
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.285
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:335 1.401
After features/support/hooks.rb:104 0.006
Tags: @product
1:31.505
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 57.265
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 25.955
And I take note of which tps features are available 0.432
Then a Tails persistence partition exists on USB drive "old" 0.579
And I shutdown Tails and wait for the computer to power off 6.842
After features/support/hooks.rb:335 0.393
After features/support/hooks.rb:104 0.009
Tags: @product
1:33.344
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.152
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.311
When I write some files expected to persist 1.582
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.359
And all persistent directories from the old Tails version have safe access rights 2.202
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 8.526
# 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" 13.449
After features/support/hooks.rb:335 0.504
After features/support/hooks.rb:104 0.010
Tags: @product
2:12.512
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.217
And I log in to a new session 13.669
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.908
Then the running Tails is installed on USB drive "to_upgrade" 15.430
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 2.748
After features/support/hooks.rb:104 0.000
Tags: @product
1:15.205
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.922
Then all tps features from the old Tails version are active 1.124
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.875
And the expected persistent files created with the old Tails version are present in the filesystem 1.299
And all persistent directories from the old Tails version have safe access rights 2.594
After features/support/hooks.rb:335 0.492
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:50.831
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.669
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.023
And Tor is ready 12.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.402
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.917
Given I shutdown Tails and wait for the computer to power off 9.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.528
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.209
When the network is plugged 0.017
And Tor is ready 11.762
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.695
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.621
Given I shutdown Tails and wait for the computer to power off 8.068
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.586
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.039
And Tor is ready 9.932
Then the Upgrader considers the system as up-to-date 10.578
# 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.154
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:335 0.645
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
19.621
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.770
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.793
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.693
After features/support/hooks.rb:335 0.564
After features/support/hooks.rb:104 0.000