Project Number Date
test_Tails_ISO_devel 4554 17 Aug 2026, 18:25

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:37.785 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:5.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.754
When I start Tails from USB drive "old" with network unplugged 48.129
Then the boot device has safe access rights 2.268
And Tails is running from USB drive "old" 0.169
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.156
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 1.454
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.694
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 48.305
Then Tails is running from USB drive "old" 0.223
And I create a persistent partition 23.791
And I take note of which tps features are available 7.796
Then a Tails persistence partition exists on USB drive "old" 0.470
And I shutdown Tails and wait for the computer to power off 4.011
After features/support/hooks.rb:339 0.150
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.029
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.997
Then Tails is running from USB drive "old" 0.226
And all tps features are active 8.554
When I write some files expected to persist 1.203
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.234
And all persistent directories from the old Tails version have safe access rights 1.535
And I take note of which tps features are available 6.347
And I shutdown Tails and wait for the computer to power off 2.890
# 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.834
After features/support/hooks.rb:339 0.317
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.859
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 8.369
And I log in to a new session 11.798
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.941
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.801
Then the running Tails is installed on USB drive "to_upgrade" 19.475
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.589
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.011
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.972
Then all tps features from the old Tails version are active 1.111
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.390
And the expected persistent files created with the old Tails version are present in the filesystem 1.263
And all persistent directories from the old Tails version have safe access rights 1.957
After features/support/hooks.rb:339 0.706
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:44.602
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.608
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.027
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.288
When the network is plugged 0.035
And Tor is ready 12.715
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.640
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.031
Given I shutdown Tails and wait for the computer to power off 6.929
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.303
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.725
And the file system changes introduced in version 6.2~testoverlayfs are present 0.191
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.237
When the network is plugged 0.023
And Tor is ready 10.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.368
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.879
Given I shutdown Tails and wait for the computer to power off 4.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.471
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 10.981
And the file system changes introduced in version 6.3~testoverlayfs are present 0.315
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.096
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.034
And Tor is ready 10.786
Then the Upgrader considers the system as up-to-date 0.107
# 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.723
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.325
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.746
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 8.232
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 10.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.007
After features/support/hooks.rb:339 1.541
After features/support/hooks.rb:108 0.000