Project Number Date
test_Tails_ISO_stable 6292 14 Apr 2026, 11:45

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:58.133 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.824
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 15.365
When I start Tails from USB drive "old" with network unplugged 52.627
Then the boot device has safe access rights 3.048
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.171
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.819
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 54.832
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 24.917
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 8.101
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.011
Tags: @product
1:31.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.879
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.245
When I write some files expected to persist 1.489
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.078
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 8.382
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.495
After features/support/hooks.rb:331 0.542
After features/support/hooks.rb:100 0.007
Tags: @product
2:18.064
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 without a persistent partition and stopped at Tails Greeter's login screen 8.401
And I log in to a new session 16.553
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.727
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.613
Then the running Tails is installed on USB drive "to_upgrade" 17.196
And I unplug USB drive "to_upgrade" 0.159
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:331 8.119
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.127
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.864
Then all tps features from the old Tails version are active 1.012
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.693
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.107
After features/support/hooks.rb:331 0.958
After features/support/hooks.rb:100 0.051
Tags: @product @automatic_upgrade
4:39.812
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.297
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.263
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.411
When the network is plugged 0.014
And Tor is ready 25.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.399
Given I shutdown Tails and wait for the computer to power off 16.456
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.848
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 1.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
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.159
# 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.244
When the network is plugged 0.049
And Tor is ready 20.510
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.476
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.574
Given I shutdown Tails and wait for the computer to power off 17.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.210
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.354
And the file system changes introduced in version 6.3~testoverlayfs are present 0.509
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.015
And Tor is ready 20.774
Then the Upgrader considers the system as up-to-date 0.168
# 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.275
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.397
After features/support/hooks.rb:331 0.735
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
29.886
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 7.840
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.141
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 21.084
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.408
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.000