Project Number Date
test_Tails_ISO_stable 6344 01 May 2026, 13:11

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:51.790 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:8.148
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.016
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.897
When I start Tails from USB drive "old" with network unplugged 49.774
Then the boot device has safe access rights 2.648
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 1.267
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.018
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 54.630
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 24.451
And I take note of which tps features are available 0.766
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.252
After features/support/hooks.rb:331 0.412
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.621
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.488
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.372
When I write some files expected to persist 1.424
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 1.980
And I take note of which tps features are available 0.201
And I shutdown Tails and wait for the computer to power off 8.230
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.972
After features/support/hooks.rb:331 0.210
After features/support/hooks.rb:100 0.008
Tags: @product
2:17.584
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 without a persistent partition and stopped at Tails Greeter's login screen 8.055
And I log in to a new session 15.795
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.241
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.151
Then the running Tails is installed on USB drive "to_upgrade" 18.275
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 3.657
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.799
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.103
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.433
Then all tps features from the old Tails version are active 0.974
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.737
And the expected persistent files created with the old Tails version are present in the filesystem 1.146
And all persistent directories from the old Tails version have safe access rights 2.161
After features/support/hooks.rb:331 1.029
After features/support/hooks.rb:100 0.008
4:47.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 22.067
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.021
And Tor is ready 23.836
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.424
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.073
Given I shutdown Tails and wait for the computer to power off 19.075
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.015
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.177
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.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.206
When the network is plugged 0.018
And Tor is ready 20.026
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.061
Given I shutdown Tails and wait for the computer to power off 17.241
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.773
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.090
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.063
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.040
And Tor is ready 19.927
Then the Upgrader considers the system as up-to-date 0.121
# 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.258
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.410
After features/support/hooks.rb:331 0.970
After features/support/hooks.rb:100 0.011
28.159
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.530
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.292
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 19.841
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 0.638
After features/support/hooks.rb:100 0.000