Project Number Date
test_Tails_ISO_stable 6630 02 Sep 2026, 18:30

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:49.162 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:1.181
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.674
When I start Tails from USB drive "old" with network unplugged 43.327
Then the boot device has safe access rights 2.299
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.409
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login 49.447
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 24.086
And I take note of which tps features are available 7.106
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 4.062
After features/support/hooks.rb:339 0.227
After features/support/hooks.rb:108 0.007
Tags: @product
1:38.717
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.475
Then Tails is running from USB drive "old" 0.289
And all tps features are active 7.745
When I write some files expected to persist 1.312
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 1.817
And I take note of which tps features are available 6.535
And I shutdown Tails and wait for the computer to power off 4.377
# 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.570
After features/support/hooks.rb:339 0.137
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.973
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 without a persistent partition and stopped at Tails Greeter's login screen 9.212
And I log in to a new session 12.668
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.713
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.038
Then the running Tails is installed on USB drive "to_upgrade" 19.813
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:339 1.783
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.444
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.230
Then all tps features from the old Tails version are active 1.335
And Tails is running from USB drive "to_upgrade" 0.424
And the boot device has safe access rights 2.529
And the expected persistent files created with the old Tails version are present in the filesystem 1.084
And all persistent directories from the old Tails version have safe access rights 1.747
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:54.724
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.815
And no SquashFS delta is installed 0.097
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.028
And Tor is ready 13.365
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.954
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.398
Given I shutdown Tails and wait for the computer to power off 6.717
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.672
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 9.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.123
# 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.218
When the network is plugged 0.023
And Tor is ready 10.556
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.889
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.773
Given I shutdown Tails and wait for the computer to power off 4.169
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.756
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 8.249
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.104
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.232
When the network is plugged 0.045
And Tor is ready 10.166
Then the Upgrader considers the system as up-to-date 10.489
# 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.727
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:339 0.671
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.496
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 8.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 8.693
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.919
After features/support/hooks.rb:339 0.780
After features/support/hooks.rb:108 0.000