Project Number Date
test_Tails_ISO_devel 4383 08 May 2026, 13:23

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:44.307 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.398
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.747
When I start Tails from USB drive "old" with network unplugged 49.841
Then the boot device has safe access rights 2.981
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 1.264
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.912
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 55.408
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 25.141
And I take note of which tps features are available 0.831
Then a Tails persistence partition exists on USB drive "old" 0.578
And I shutdown Tails and wait for the computer to power off 8.573
After features/support/hooks.rb:331 0.620
After features/support/hooks.rb:100 0.012
Tags: @product
1:32.492
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.733
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.194
When I write some files expected to persist 1.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.444
And all persistent directories from the old Tails version have safe access rights 2.154
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 8.172
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.843
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.009
Tags: @product
2:12.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.257
And I log in to a new session 11.755
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.768
And I plug USB drive "to_upgrade" 2.301
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.134
Then the running Tails is installed on USB drive "to_upgrade" 17.261
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.146
After features/support/hooks.rb:331 2.101
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.320
Then all tps features from the old Tails version are active 1.045
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 3.032
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.214
After features/support/hooks.rb:331 0.839
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:38.791
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 8.850
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.016
And Tor is ready 20.979
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.897
Given I shutdown Tails and wait for the computer to power off 7.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.227
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.156
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.217
When the network is plugged 0.017
And Tor is ready 21.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.626
Given I shutdown Tails and wait for the computer to power off 17.932
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.302
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.269
And the file system changes introduced in version 6.3~testoverlayfs are present 0.340
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.017
And Tor is ready 21.681
Then the Upgrader considers the system as up-to-date 0.144
# 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 6.104
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.527
After features/support/hooks.rb:331 0.707
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
27.512
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 7.939
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.320
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 18.691
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.413
After features/support/hooks.rb:331 1.041
After features/support/hooks.rb:100 0.000