Project Number Date
test_Tails_ISO_21603-fragnesia 4 16 May 2026, 17:29

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 10:55.617 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:3.177
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.485
When I start Tails from USB drive "old" with network unplugged 46.385
Then the boot device has safe access rights 2.577
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:335 1.198
After features/support/hooks.rb:104 0.006
Tags: @product
1:21.176
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 51.513
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 24.481
And I take note of which tps features are available 0.325
Then a Tails persistence partition exists on USB drive "old" 0.521
And I shutdown Tails and wait for the computer to power off 4.030
After features/support/hooks.rb:335 0.226
After features/support/hooks.rb:104 0.007
Tags: @product
1:23.761
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.134
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.156
When I write some files expected to persist 1.232
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.306
And all persistent directories from the old Tails version have safe access rights 1.768
And I take note of which tps features are available 0.128
And I shutdown Tails and wait for the computer to power off 7.915
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 11.642
After features/support/hooks.rb:335 0.552
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.233
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.888
And I log in to a new session 12.059
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.661
And I plug USB drive "to_upgrade" 2.204
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.452
Then the running Tails is installed on USB drive "to_upgrade" 14.628
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:335 1.989
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.200
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.371
Then all tps features from the old Tails version are active 0.903
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.559
And the expected persistent files created with the old Tails version are present in the filesystem 1.177
And all persistent directories from the old Tails version have safe access rights 1.822
After features/support/hooks.rb:335 0.581
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:31.740
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.841
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.014
And Tor is ready 13.210
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.356
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.412
Given I shutdown Tails and wait for the computer to power off 9.270
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.998
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.195
When the network is plugged 0.014
And Tor is ready 10.923
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.738
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.207
Given I shutdown Tails and wait for the computer to power off 7.850
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.266
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.024
And Tor is ready 11.078
Then the Upgrader considers the system as up-to-date 10.530
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:335 0.683
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.326
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.198
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.045
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.996
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.805
After features/support/hooks.rb:335 0.916
After features/support/hooks.rb:104 0.000