Project Number Date
test_Tails_ISO_stable 6339 30 Apr 2026, 15:51

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:43.887 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:5.798
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.877
When I start Tails from USB drive "old" with network unplugged 45.024
Then the boot device has safe access rights 3.808
And Tails is running from USB drive "old" 0.327
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.318
And I unplug USB drive "old" 0.159
After features/support/hooks.rb:331 3.963
After features/support/hooks.rb:100 0.011
Tags: @product
1:27.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 56.573
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 25.121
And I take note of which tps features are available 0.873
Then a Tails persistence partition exists on USB drive "old" 0.655
And I shutdown Tails and wait for the computer to power off 4.334
After features/support/hooks.rb:331 0.474
After features/support/hooks.rb:100 0.007
Tags: @product
1:34.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.598
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.404
When I write some files expected to persist 1.573
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.509
And all persistent directories from the old Tails version have safe access rights 2.212
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 8.133
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.870
After features/support/hooks.rb:331 0.337
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.981
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.935
And I log in to a new session 13.722
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.810
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.966
Then the running Tails is installed on USB drive "to_upgrade" 16.976
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 3.690
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.494
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.305
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 3.064
And the expected persistent files created with the old Tails version are present in the filesystem 1.303
And all persistent directories from the old Tails version have safe access rights 2.403
After features/support/hooks.rb:331 0.892
After features/support/hooks.rb:100 0.037
Tags: @product @automatic_upgrade
4:39.287
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.595
And no SquashFS delta is installed 0.071
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
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.211
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.021
And Tor is ready 23.239
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.124
Given I shutdown Tails and wait for the computer to power off 20.618
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.914
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.148
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.200
When the network is plugged 0.013
And Tor is ready 21.660
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.408
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.257
Given I shutdown Tails and wait for the computer to power off 13.965
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.304
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.284
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.233
When the network is plugged 0.035
And Tor is ready 21.517
Then the Upgrader considers the system as up-to-date 0.123
# 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.600
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.601
After features/support/hooks.rb:331 0.875
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
27.332
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 with a persistent partition enabled and logged in 8.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 18.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.426
After features/support/hooks.rb:331 1.097
After features/support/hooks.rb:100 0.000