Project Number Date
test_Tails_ISO_stable 6112 01 Feb 2026, 11:36

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:29.133 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:47.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.434
When I start Tails from USB drive "old" with network unplugged 1:27.733
Then the boot device has safe access rights 3.108
And Tails is running from USB drive "old" 0.306
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.165
After features/support/hooks.rb:331 3.815
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.013
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 56.965
Then Tails is running from USB drive "old" 0.258
And I create a persistent partition 24.448
And I take note of which tps features are available 0.802
Then a Tails persistence partition exists on USB drive "old" 0.550
And I shutdown Tails and wait for the computer to power off 7.935
After features/support/hooks.rb:331 0.407
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.688
Then Tails is running from USB drive "old" 0.419
And all tps features are active 1.476
When I write some files expected to persist 1.344
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.312
And all persistent directories from the old Tails version have safe access rights 2.143
And I take note of which tps features are available 0.196
And I shutdown Tails and wait for the computer to power off 8.006
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.842
After features/support/hooks.rb:331 0.115
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.995
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 without a persistent partition and stopped at Tails Greeter's login screen 9.022
And I log in to a new session 13.276
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.770
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.961
Then the running Tails is installed on USB drive "to_upgrade" 17.367
And I unplug USB drive "to_upgrade" 0.172
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:331 3.694
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.608
Then all tps features from the old Tails version are active 0.891
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.235
And all persistent directories from the old Tails version have safe access rights 2.107
After features/support/hooks.rb:331 0.823
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:51.907
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 8.911
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.297
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.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.021
And Tor is ready 13.322
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.200
Given I shutdown Tails and wait for the computer to power off 14.545
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.911
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.231
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.143
# 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.215
When the network is plugged 0.015
And Tor is ready 10.314
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.145
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.344
Given I shutdown Tails and wait for the computer to power off 7.988
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.320
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.211
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.015
And Tor is ready 10.189
Then the Upgrader considers the system as up-to-date 10.654
# 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.308
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.375
After features/support/hooks.rb:331 0.659
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
21.919
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.400
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.998
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.962
After features/support/hooks.rb:331 0.847
After features/support/hooks.rb:100 0.000