Project Number Date
test_Tails_ISO_stable 6332 29 Apr 2026, 11:28

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:18.738 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.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 12.721
When I start Tails from USB drive "old" with network unplugged 52.128
Then the boot device has safe access rights 2.531
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.144
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.300
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.793
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 22.996
And I take note of which tps features are available 0.671
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 7.983
After features/support/hooks.rb:331 0.582
After features/support/hooks.rb:100 0.018
Tags: @product
1:27.848
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.439
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.297
When I write some files expected to persist 1.284
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 1.787
And I take note of which tps features are available 0.133
And I shutdown Tails and wait for the computer to power off 7.833
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.081
After features/support/hooks.rb:331 0.453
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.539
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 7.996
And I log in to a new session 12.314
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.686
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.402
Then the running Tails is installed on USB drive "to_upgrade" 14.606
And I unplug USB drive "to_upgrade" 0.154
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 2.131
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.516
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.722
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.304
And the boot device has safe access rights 2.565
And the expected persistent files created with the old Tails version are present in the filesystem 1.178
And all persistent directories from the old Tails version have safe access rights 1.764
After features/support/hooks.rb:331 0.650
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
4:30.986
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 8.163
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.342
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.365
When the network is plugged 0.016
And Tor is ready 21.113
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.059
Given I shutdown Tails and wait for the computer to power off 14.577
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.685
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.085
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.204
When the network is plugged 0.017
And Tor is ready 21.397
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.504
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.137
Given I shutdown Tails and wait for the computer to power off 18.622
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.110
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 0.992
And the file system changes introduced in version 6.3~testoverlayfs are present 0.381
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.189
When the network is plugged 0.014
And Tor is ready 20.538
Then the Upgrader considers the system as up-to-date 0.110
# 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.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.334
After features/support/hooks.rb:331 0.897
After features/support/hooks.rb:100 0.039
Tags: @product @automatic_upgrade
24.440
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.365
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 16.344
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.386
After features/support/hooks.rb:331 0.951
After features/support/hooks.rb:100 0.000