Project Number Date
test_Tails_ISO_stable 6733 09 Oct 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 11:26.071 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:13.445
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.728
When I start Tails from USB drive "old" with network unplugged 56.000
Then the boot device has safe access rights 2.101
And Tails is running from USB drive "old" 0.175
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.129
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.622
After features/support/hooks.rb:108 0.005
Tags: @product
1:21.278
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 47.331
Then Tails is running from USB drive "old" 0.178
And I create a persistent partition 22.768
And I take note of which tps features are available 6.417
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 3.992
After features/support/hooks.rb:339 0.567
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.047
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.539
Then Tails is running from USB drive "old" 0.239
And all tps features are active 7.933
When I write some files expected to persist 1.219
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.315
And all persistent directories from the old Tails version have safe access rights 1.481
And I take note of which tps features are available 5.795
And I shutdown Tails and wait for the computer to power off 2.512
# 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.752
After features/support/hooks.rb:339 0.300
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.054
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.597
And I log in to a new session 12.129
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.624
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.387
Then the running Tails is installed on USB drive "to_upgrade" 17.828
And I unplug USB drive "to_upgrade" 0.122
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.996
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.812
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.100
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.444
Then all tps features from the old Tails version are active 1.129
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.145
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 1.628
After features/support/hooks.rb:339 0.831
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:42.887
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 with a persistent partition enabled and logged in 21.219
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
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.183
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.036
And Tor is ready 13.348
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.324
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.489
Given I shutdown Tails and wait for the computer to power off 5.195
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.304
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.208
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.035
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.092
# 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.214
When the network is plugged 0.037
And Tor is ready 10.279
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.909
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.936
Given I shutdown Tails and wait for the computer to power off 4.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.631
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.727
And the file system changes introduced in version 6.3~testoverlayfs are present 0.285
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.030
And Tor is ready 10.396
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 3.159
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.304
After features/support/hooks.rb:339 0.948
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
18.545
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 with a persistent partition enabled and logged in 7.779
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
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.079
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 10.071
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.340
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.000