Project Number Date
test_Tails_ISO_stable 6583 17 Aug 2026, 11:34

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:5.707 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:20.408
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.141
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.439
When I start Tails from USB drive "old" with network unplugged 1:2.735
Then the boot device has safe access rights 2.302
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:339 1.304
After features/support/hooks.rb:108 0.005
Tags: @product
1:25.612
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 50.964
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 24.208
And I take note of which tps features are available 6.912
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 2.624
After features/support/hooks.rb:339 0.263
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.278
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.613
Then Tails is running from USB drive "old" 0.239
And all tps features are active 7.495
When I write some files expected to persist 1.189
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.284
And all persistent directories from the old Tails version have safe access rights 1.704
And I take note of which tps features are available 6.497
And I shutdown Tails and wait for the computer to power off 2.565
# 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.376
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.006
Tags: @product
2:28.091
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 21.914
And I log in to a new session 12.232
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.032
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.838
Then the running Tails is installed on USB drive "to_upgrade" 18.592
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.594
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.600
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.571
Then all tps features from the old Tails version are active 1.074
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.156
And the expected persistent files created with the old Tails version are present in the filesystem 0.825
And all persistent directories from the old Tails version have safe access rights 1.601
After features/support/hooks.rb:339 0.585
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:42.789
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.324
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.226
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.359
When the network is plugged 0.029
And Tor is ready 13.541
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.074
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.915
Given I shutdown Tails and wait for the computer to power off 5.410
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.173
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.014
And the file system changes introduced in version 6.2~testoverlayfs are present 0.333
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.317
When the network is plugged 0.024
And Tor is ready 10.871
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.857
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.270
Given I shutdown Tails and wait for the computer to power off 2.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.151
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 8.439
And the file system changes introduced in version 6.3~testoverlayfs are present 0.342
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.025
And Tor is ready 10.737
Then the Upgrader considers the system as up-to-date 10.402
# 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.133
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:339 0.682
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
19.926
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.205
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.863
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.493
After features/support/hooks.rb:339 0.806
After features/support/hooks.rb:108 0.000