Project Number Date
test_Tails_ISO_devel 4488 10 Jul 2026, 11:13

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:30.327 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.773
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 12.934
When I start Tails from USB drive "old" with network unplugged 43.679
Then the boot device has safe access rights 2.468
And Tails is running from USB drive "old" 0.232
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.385
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.535
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 51.912
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.647
And I take note of which tps features are available 3.866
Then a Tails persistence partition exists on USB drive "old" 0.615
And I shutdown Tails and wait for the computer to power off 8.165
After features/support/hooks.rb:339 0.348
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.945
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.558
Then Tails is running from USB drive "old" 0.220
And all tps features are active 4.803
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.276
And all persistent directories from the old Tails version have safe access rights 1.995
And I take note of which tps features are available 3.686
And I shutdown Tails and wait for the computer to power off 8.057
# 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.921
After features/support/hooks.rb:339 0.424
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.362
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 without a persistent partition and stopped at Tails Greeter's login screen 7.671
And I log in to a new session 12.810
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.729
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.555
Then the running Tails is installed on USB drive "to_upgrade" 14.113
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:339 1.998
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.983
Then all tps features from the old Tails version are active 0.867
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.445
And the expected persistent files created with the old Tails version are present in the filesystem 1.138
And all persistent directories from the old Tails version have safe access rights 1.920
After features/support/hooks.rb:339 0.632
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:47.506
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.118
And no SquashFS delta is installed 0.055
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.242
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.020
And Tor is ready 12.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.970
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.082
Given I shutdown Tails and wait for the computer to power off 9.545
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.062
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.590
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.211
When the network is plugged 0.016
And Tor is ready 9.820
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.992
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.504
Given I shutdown Tails and wait for the computer to power off 8.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.059
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.806
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.241
When the network is plugged 0.017
And Tor is ready 10.662
Then the Upgrader considers the system as up-to-date 10.525
# 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.884
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 0.954
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.577
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 7.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.097
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.056
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.676
After features/support/hooks.rb:339 0.637
After features/support/hooks.rb:108 0.000