Project Number Date
test_Tails_ISO_stable 6236 26 Mar 2026, 07:02

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 13:16.510 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:21.904
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.880
When I start Tails from USB drive "old" with network unplugged 1:3.481
Then the boot device has safe access rights 2.754
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:331 3.673
After features/support/hooks.rb:100 0.034
Tags: @product
1:30.075
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 55.106
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 25.222
And I take note of which tps features are available 0.722
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 8.164
After features/support/hooks.rb:331 0.306
After features/support/hooks.rb:100 0.019
Tags: @product
1:30.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.533
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.024
When I write some files expected to persist 1.277
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.435
And all persistent directories from the old Tails version have safe access rights 2.047
And I take note of which tps features are available 0.178
And I shutdown Tails and wait for the computer to power off 8.179
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.633
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.674
And I log in to a new session 14.340
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.069
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.947
Then the running Tails is installed on USB drive "to_upgrade" 16.207
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 2.407
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.996
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.712
Then all tps features from the old Tails version are active 0.960
And Tails is running from USB drive "to_upgrade" 0.327
And the boot device has safe access rights 2.760
And the expected persistent files created with the old Tails version are present in the filesystem 1.188
And all persistent directories from the old Tails version have safe access rights 1.971
After features/support/hooks.rb:331 0.885
After features/support/hooks.rb:100 0.006
5:0.462
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 8.148
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
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.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.018
And Tor is ready 22.112
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.414
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.297
Given I shutdown Tails and wait for the computer to power off 20.142
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.330
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.176
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.087
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.183
When the network is plugged 0.013
And Tor is ready 40.905
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.142
Given I shutdown Tails and wait for the computer to power off 17.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.883
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.500
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.158
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.034
And Tor is ready 21.338
Then the Upgrader considers the system as up-to-date 0.129
# 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.323
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:331 0.955
After features/support/hooks.rb:100 0.010
25.468
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.447
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 17.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 0.758
After features/support/hooks.rb:100 0.000