Project Number Date
test_Tails_ISO_stable 6047 08 Jan 2026, 19:21

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 11:34.376 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:22.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.858
When I start Tails from USB drive "old" with network unplugged 1:3.641
Then the boot device has safe access rights 3.274
And Tails is running from USB drive "old" 0.295
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 3.664
After features/support/hooks.rb:100 0.013
Tags: @product
1:24.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.335
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 24.561
And I take note of which tps features are available 0.709
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 4.209
After features/support/hooks.rb:331 0.589
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.375
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.762
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.340
When I write some files expected to persist 1.429
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.175
And I take note of which tps features are available 0.241
And I shutdown Tails and wait for the computer to power off 8.531
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.932
After features/support/hooks.rb:331 0.533
After features/support/hooks.rb:100 0.011
Tags: @product
2:16.877
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 9.216
And I log in to a new session 13.986
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.078
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.851
Then the running Tails is installed on USB drive "to_upgrade" 17.200
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:331 4.100
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.815
Then all tps features from the old Tails version are active 0.995
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.837
And the expected persistent files created with the old Tails version are present in the filesystem 1.065
And all persistent directories from the old Tails version have safe access rights 1.897
After features/support/hooks.rb:331 0.747
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:31.858
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.561
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.460
When the network is plugged 0.019
And Tor is ready 12.698
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.478
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.332
Given I shutdown Tails and wait for the computer to power off 9.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.350
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.190
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.235
When the network is plugged 0.020
And Tor is ready 11.049
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.255
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.362
Given I shutdown Tails and wait for the computer to power off 8.662
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.937
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.421
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.268
When the network is plugged 0.032
And Tor is ready 11.165
Then the Upgrader considers the system as up-to-date 0.185
# 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.244
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.430
After features/support/hooks.rb:331 1.080
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
18.881
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.811
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.321
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.357
After features/support/hooks.rb:331 0.897
After features/support/hooks.rb:100 0.000