Project Number Date
test_Tails_ISO_stable 6211 17 Mar 2026, 11: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 13:31.954 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:33.655
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.542
When I start Tails from USB drive "old" with network unplugged 1:14.313
Then the boot device has safe access rights 2.888
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.167
After features/support/hooks.rb:331 1.410
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 55.626
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 25.042
And I take note of which tps features are available 0.835
Then a Tails persistence partition exists on USB drive "old" 0.637
And I shutdown Tails and wait for the computer to power off 8.299
After features/support/hooks.rb:331 0.624
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.813
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.217
When I write some files expected to persist 1.404
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.478
And all persistent directories from the old Tails version have safe access rights 2.111
And I take note of which tps features are available 0.186
And I shutdown Tails and wait for the computer to power off 8.620
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.655
After features/support/hooks.rb:331 0.261
After features/support/hooks.rb:100 0.009
Tags: @product
2:22.760
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 without a persistent partition and stopped at Tails Greeter's login screen 10.116
And I log in to a new session 14.643
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.011
And I plug USB drive "to_upgrade" 2.282
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.243
Then the running Tails is installed on USB drive "to_upgrade" 18.754
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.492
After features/support/hooks.rb:331 2.791
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.660
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:8.110
Then all tps features from the old Tails version are active 0.994
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.681
And the expected persistent files created with the old Tails version are present in the filesystem 1.379
And all persistent directories from the old Tails version have safe access rights 2.187
After features/support/hooks.rb:331 0.587
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
4:48.693
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.835
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.234
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.018
And Tor is ready 24.142
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.133
Given I shutdown Tails and wait for the computer to power off 20.134
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.887
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
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.136
# 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.270
When the network is plugged 0.026
And Tor is ready 21.657
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.407
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.944
Given I shutdown Tails and wait for the computer to power off 13.826
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.538
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.167
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.113
# 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.234
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.026
And Tor is ready 22.138
Then the Upgrader considers the system as up-to-date 0.103
# 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 5.019
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:331 1.018
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
26.257
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 7.786
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.400
After features/support/hooks.rb:331 0.990
After features/support/hooks.rb:100 0.000