Project Number Date
test_Tails_ISO_stable 6728 07 Oct 2026, 14:01

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:37.691 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:11.380
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.925
When I start Tails from USB drive "old" with network unplugged 53.025
Then the boot device has safe access rights 2.577
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.712
After features/support/hooks.rb:108 0.012
Tags: @product
1:26.782
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login 49.712
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 24.812
And I take note of which tps features are available 7.366
Then a Tails persistence partition exists on USB drive "old" 0.571
And I shutdown Tails and wait for the computer to power off 3.983
After features/support/hooks.rb:339 0.592
After features/support/hooks.rb:108 0.006
Tags: @product
1:38.864
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.836
Then Tails is running from USB drive "old" 0.493
And all tps features are active 7.569
When I write some files expected to persist 1.538
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.145
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.678
And I take note of which tps features are available 6.436
And I shutdown Tails and wait for the computer to power off 4.142
# 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" 11.608
After features/support/hooks.rb:339 0.403
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.272
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.750
And I log in to a new session 11.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.773
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.865
Then the running Tails is installed on USB drive "to_upgrade" 18.990
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.109
After features/support/hooks.rb:339 1.806
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.851
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.590
Then all tps features from the old Tails version are active 1.043
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.266
And the expected persistent files created with the old Tails version are present in the filesystem 0.963
And all persistent directories from the old Tails version have safe access rights 1.689
After features/support/hooks.rb:339 0.863
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.761
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.655
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.022
And Tor is ready 13.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.331
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.457
Given I shutdown Tails and wait for the computer to power off 5.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.012
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.471
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.171
When the network is plugged 0.023
And Tor is ready 10.439
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.080
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.328
Given I shutdown Tails and wait for the computer to power off 4.186
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.525
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.387
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.091
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.199
When the network is plugged 0.027
And Tor is ready 10.414
Then the Upgrader considers the system as up-to-date 0.090
# 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.244
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.399
After features/support/hooks.rb:339 0.734
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.779
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.313
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.092
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 10.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.329
After features/support/hooks.rb:339 0.972
After features/support/hooks.rb:108 0.000