Project Number Date
test_Tails_ISO_devel 4294 26 Mar 2026, 11:04

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:22.659 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.094
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.392
When I start Tails from USB drive "old" with network unplugged 54.128
Then the boot device has safe access rights 2.752
And Tails is running from USB drive "old" 0.243
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 1.434
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.836
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 54.318
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.758
And I take note of which tps features are available 0.633
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 4.241
After features/support/hooks.rb:331 0.500
After features/support/hooks.rb:100 0.006
Tags: @product
1:19.382
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.409
Then Tails is running from USB drive "old" 0.269
And all tps features are active 1.276
When I write some files expected to persist 1.328
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.153
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 1.790
And I take note of which tps features are available 0.158
And I shutdown Tails and wait for the computer to power off 3.894
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.582
After features/support/hooks.rb:331 0.487
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.776
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.880
And I log in to a new session 11.579
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.743
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.311
Then the running Tails is installed on USB drive "to_upgrade" 15.754
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:331 1.815
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.272
Then all tps features from the old Tails version are active 0.960
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.372
And the expected persistent files created with the old Tails version are present in the filesystem 1.147
And all persistent directories from the old Tails version have safe access rights 1.772
After features/support/hooks.rb:331 0.944
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
4:45.792
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.303
And no SquashFS delta is installed 0.116
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.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.016
And Tor is ready 19.586
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.372
Given I shutdown Tails and wait for the computer to power off 19.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.631
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.201
When the network is plugged 0.017
And Tor is ready 41.014
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.726
Given I shutdown Tails and wait for the computer to power off 17.079
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.265
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.303
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.327
When the network is plugged 0.018
And Tor is ready 21.167
Then the Upgrader considers the system as up-to-date 0.146
# 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.217
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
24.961
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.314
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 16.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.345
After features/support/hooks.rb:331 0.766
After features/support/hooks.rb:100 0.000