Project Number Date
test_Tails_ISO_stable 6731 08 Oct 2026, 16:02

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:52.780 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.584
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 13.900
When I start Tails from USB drive "old" with network unplugged 50.419
Then the boot device has safe access rights 2.467
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.481
After features/support/hooks.rb:108 0.026
Tags: @product
1:27.587
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login 51.387
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 24.507
And I take note of which tps features are available 6.904
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 3.913
After features/support/hooks.rb:339 0.243
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.775
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.525
Then Tails is running from USB drive "old" 0.227
And all tps features are active 8.488
When I write some files expected to persist 1.273
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.273
And all persistent directories from the old Tails version have safe access rights 1.897
And I take note of which tps features are available 6.109
And I shutdown Tails and wait for the computer to power off 4.029
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.655
After features/support/hooks.rb:339 0.580
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.649
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.638
And I log in to a new session 13.219
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.906
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.841
Then the running Tails is installed on USB drive "to_upgrade" 19.557
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.788
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.097
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.819
Then all tps features from the old Tails version are active 1.296
And Tails is running from USB drive "to_upgrade" 0.260
And the boot device has safe access rights 2.389
And the expected persistent files created with the old Tails version are present in the filesystem 1.173
And all persistent directories from the old Tails version have safe access rights 2.053
After features/support/hooks.rb:339 0.620
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:47.964
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.651
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.342
When the network is plugged 0.041
And Tor is ready 13.275
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.340
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.947
Given I shutdown Tails and wait for the computer to power off 5.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.799
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.564
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.184
When the network is plugged 0.037
And Tor is ready 10.821
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.566
Given I shutdown Tails and wait for the computer to power off 4.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.048
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 9.012
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.041
And Tor is ready 10.255
Then the Upgrader considers the system as up-to-date 10.442
# 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 3.749
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.912
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.121
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.019
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 10.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.311
After features/support/hooks.rb:339 0.584
After features/support/hooks.rb:108 0.000