Project Number Date
test_Tails_ISO_stable 6722 05 Oct 2026, 12:26

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.212 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:15.138
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 14.010
When I start Tails from USB drive "old" with network unplugged 56.777
Then the boot device has safe access rights 2.523
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.417
After features/support/hooks.rb:108 0.071
Tags: @product
1:26.247
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "old" with network unplugged and I login 49.042
Then Tails is running from USB drive "old" 0.225
And I create a persistent partition 24.973
And I take note of which tps features are available 7.332
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 4.035
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.575
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.787
Then Tails is running from USB drive "old" 0.381
And all tps features are active 7.985
When I write some files expected to persist 1.382
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.304
And all persistent directories from the old Tails version have safe access rights 1.551
And I take note of which tps features are available 6.523
And I shutdown Tails and wait for the computer to power off 2.810
# 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.581
After features/support/hooks.rb:339 0.224
After features/support/hooks.rb:108 0.005
Tags: @product
2:16.967
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 8.952
And I log in to a new session 11.361
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.601
Then the running Tails is installed on USB drive "to_upgrade" 20.019
And I unplug USB drive "to_upgrade" 1.015
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:339 3.791
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.543
Then all tps features from the old Tails version are active 3.853
And Tails is running from USB drive "to_upgrade" 0.191
And the boot device has safe access rights 2.697
And the expected persistent files created with the old Tails version are present in the filesystem 2.634
And all persistent directories from the old Tails version have safe access rights 1.614
After features/support/hooks.rb:339 0.611
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:40.345
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.546
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.294
When the network is plugged 0.036
And Tor is ready 12.254
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.085
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.660
Given I shutdown Tails and wait for the computer to power off 5.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.228
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 10.197
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.112
# 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.219
When the network is plugged 0.108
And Tor is ready 10.340
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.333
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.488
Given I shutdown Tails and wait for the computer to power off 4.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.190
Then Tails is running version 6.3~testoverlayfs 0.021
And all tps features are active 8.313
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.196
When the network is plugged 0.024
And Tor is ready 10.652
Then the Upgrader considers the system as up-to-date 0.097
# 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.186
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.445
After features/support/hooks.rb:339 1.283
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.320
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.341
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.669
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.916
After features/support/hooks.rb:339 0.885
After features/support/hooks.rb:108 0.000