Project Number Date
test_Tails_ISO_stable 6530 25 Jul 2026, 11:41

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.157 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.696
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.292
When I start Tails from USB drive "old" with network unplugged 42.789
Then the boot device has safe access rights 2.746
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.445
After features/support/hooks.rb:108 0.065
Tags: @product
1:28.970
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 54.017
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 25.151
And I take note of which tps features are available 4.710
Then a Tails persistence partition exists on USB drive "old" 0.631
And I shutdown Tails and wait for the computer to power off 4.178
After features/support/hooks.rb:339 0.418
After features/support/hooks.rb:108 0.008
Tags: @product
1:37.557
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.441
Then Tails is running from USB drive "old" 0.278
And all tps features are active 5.328
When I write some files expected to persist 1.363
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.413
And all persistent directories from the old Tails version have safe access rights 1.903
And I take note of which tps features are available 4.071
And I shutdown Tails and wait for the computer to power off 4.092
# 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.386
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.949
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 without a persistent partition and stopped at Tails Greeter's login screen 7.854
And I log in to a new session 12.820
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.746
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.270
Then the running Tails is installed on USB drive "to_upgrade" 15.719
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:339 2.185
After features/support/hooks.rb:108 0.000
Tags: @product
1:15.941
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.931
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.546
And the expected persistent files created with the old Tails version are present in the filesystem 1.116
And all persistent directories from the old Tails version have safe access rights 1.895
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
3:55.822
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.127
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.018
And Tor is ready 12.746
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.788
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.961
Given I shutdown Tails and wait for the computer to power off 6.765
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.762
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.556
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.214
When the network is plugged 0.016
And Tor is ready 10.515
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.697
Given I shutdown Tails and wait for the computer to power off 4.052
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.158
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.988
And the file system changes introduced in version 6.3~testoverlayfs are present 0.357
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.170
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.014
And Tor is ready 10.132
Then the Upgrader considers the system as up-to-date 10.614
# 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 4.697
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.346
After features/support/hooks.rb:339 0.737
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
21.220
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 with a persistent partition enabled and logged in 7.518
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
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.050
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.317
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.071
After features/support/hooks.rb:339 0.993
After features/support/hooks.rb:108 0.000