Project Number Date
test_Tails_ISO_stable 6216 19 Mar 2026, 06: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 12:12.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:12.145
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.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.905
When I start Tails from USB drive "old" with network unplugged 53.229
Then the boot device has safe access rights 3.100
And Tails is running from USB drive "old" 0.270
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.251
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:331 1.541
After features/support/hooks.rb:100 0.011
Tags: @product
1:25.557
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 55.240
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.335
And I take note of which tps features are available 0.871
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 4.155
After features/support/hooks.rb:331 0.293
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.987
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.037
When I write some files expected to persist 1.195
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 1.690
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.008
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.993
After features/support/hooks.rb:331 0.335
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.412
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 without a persistent partition and stopped at Tails Greeter's login screen 8.576
And I log in to a new session 9.694
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.703
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.926
Then the running Tails is installed on USB drive "to_upgrade" 15.960
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:331 2.361
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.029
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.679
Then all tps features from the old Tails version are active 0.860
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 2.351
And the expected persistent files created with the old Tails version are present in the filesystem 1.020
And all persistent directories from the old Tails version have safe access rights 1.879
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:28.480
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 8.271
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.016
And Tor is ready 20.661
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.409
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.474
Given I shutdown Tails and wait for the computer to power off 19.729
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.462
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 1.102
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.205
When the network is plugged 0.016
And Tor is ready 20.903
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.946
Given I shutdown Tails and wait for the computer to power off 17.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.506
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.082
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.168
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.018
And Tor is ready 19.978
Then the Upgrader considers the system as up-to-date 0.106
# 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.317
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.332
After features/support/hooks.rb:331 0.919
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
23.929
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.599
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 15.677
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.794
After features/support/hooks.rb:100 0.000