Project Number Date
test_Tails_ISO_stable 6461 18 Jun 2026, 07:55

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:2.952 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:0.311
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.123
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 13.653
When I start Tails from USB drive "old" with network unplugged 42.427
Then the boot device has safe access rights 2.391
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:339 1.304
After features/support/hooks.rb:108 0.018
Tags: @product
1:34.068
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login 54.557
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 25.008
And I take note of which tps features are available 4.963
Then a Tails persistence partition exists on USB drive "old" 0.642
And I shutdown Tails and wait for the computer to power off 8.551
After features/support/hooks.rb:339 0.258
After features/support/hooks.rb:108 0.022
Tags: @product
1:34.557
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.114
Then Tails is running from USB drive "old" 0.251
And all tps features are active 5.038
When I write some files expected to persist 1.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.983
And I take note of which tps features are available 3.972
And I shutdown Tails and wait for the computer to power off 2.828
# 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.274
After features/support/hooks.rb:339 0.268
After features/support/hooks.rb:108 0.046
Tags: @product
2:12.206
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.625
And I log in to a new session 12.546
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.612
Then the running Tails is installed on USB drive "to_upgrade" 16.093
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:339 0.725
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.795
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.120
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.622
Then all tps features from the old Tails version are active 1.106
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.116
And all persistent directories from the old Tails version have safe access rights 1.836
After features/support/hooks.rb:339 0.972
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
4:3.431
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.553
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.017
And Tor is ready 12.865
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.732
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.099
Given I shutdown Tails and wait for the computer to power off 9.838
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.600
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 5.844
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.191
When the network is plugged 0.015
And Tor is ready 11.517
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.241
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.231
Given I shutdown Tails and wait for the computer to power off 6.997
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.772
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 4.997
And the file system changes introduced in version 6.3~testoverlayfs are present 0.325
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.200
When the network is plugged 0.016
And Tor is ready 10.325
Then the Upgrader considers the system as up-to-date 10.524
# 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 4.452
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.982
After features/support/hooks.rb:108 0.042
Tags: @product @automatic_upgrade
22.582
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.583
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.339
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.192
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.335
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.000