Project Number Date
test_Tails_ISO_stable 6402 25 May 2026, 11:20

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:3.976 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:2.953
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 12.804
When I start Tails from USB drive "old" with network unplugged 45.714
Then the boot device has safe access rights 2.633
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:335 1.317
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.180
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 53.678
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 24.308
And I take note of which tps features are available 0.357
Then a Tails persistence partition exists on USB drive "old" 0.497
And I shutdown Tails and wait for the computer to power off 8.078
After features/support/hooks.rb:335 0.229
After features/support/hooks.rb:104 0.007
Tags: @product
1:23.428
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.818
Then Tails is running from USB drive "old" 0.221
And all tps features are active 1.041
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.171
And all persistence configuration files have safe access rights 0.268
And all persistent directories from the old Tails version have safe access rights 1.860
And I take note of which tps features are available 0.299
And I shutdown Tails and wait for the computer to power off 7.933
# 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.560
After features/support/hooks.rb:335 0.477
After features/support/hooks.rb:104 0.023
Tags: @product
2:8.995
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.016
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.053
And I log in to a new session 12.171
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.865
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.991
Then the running Tails is installed on USB drive "to_upgrade" 14.374
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:335 2.122
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.173
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.576
Then all tps features from the old Tails version are active 0.897
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.465
And the expected persistent files created with the old Tails version are present in the filesystem 1.061
And all persistent directories from the old Tails version have safe access rights 1.877
After features/support/hooks.rb:335 0.530
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:35.248
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.276
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.018
And Tor is ready 13.260
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.502
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.124
Given I shutdown Tails and wait for the computer to power off 9.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.947
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.202
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.216
When the network is plugged 0.014
And Tor is ready 9.970
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.878
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.746
Given I shutdown Tails and wait for the computer to power off 8.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.505
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.017
And Tor is ready 11.063
Then the Upgrader considers the system as up-to-date 10.494
# 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.750
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.333
After features/support/hooks.rb:335 0.776
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
18.995
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.367
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.707
After features/support/hooks.rb:335 0.744
After features/support/hooks.rb:104 0.000