Project Number Date
test_Tails_ISO_devel 4446 14 Jun 2026, 11:22

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:10.922 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:8.037
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.135
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.083
And I write an old version of the Tails USB image to disk "old" 13.432
When I start Tails from USB drive "old" with network unplugged 49.638
Then the boot device has safe access rights 2.844
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.232
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:339 3.562
After features/support/hooks.rb:108 0.016
Tags: @product
1:28.613
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login 54.949
Then Tails is running from USB drive "old" 0.345
And I create a persistent partition 25.763
And I take note of which tps features are available 4.152
Then a Tails persistence partition exists on USB drive "old" 0.487
And I shutdown Tails and wait for the computer to power off 2.792
After features/support/hooks.rb:339 0.290
After features/support/hooks.rb:108 0.017
Tags: @product
1:42.012
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.630
Then Tails is running from USB drive "old" 0.329
And all tps features are active 5.269
When I write some files expected to persist 1.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.124
And I take note of which tps features are available 4.370
And I shutdown Tails and wait for the computer to power off 8.623
# 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.698
After features/support/hooks.rb:339 0.341
After features/support/hooks.rb:108 0.016
Tags: @product
2:12.504
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.035
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.159
And I log in to a new session 12.580
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.072
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.228
Then the running Tails is installed on USB drive "to_upgrade" 15.957
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 1.986
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.301
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.117
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.884
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.263
And the boot device has safe access rights 2.756
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 1.947
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
4:4.598
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.342
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.016
And Tor is ready 12.686
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.507
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.607
Given I shutdown Tails and wait for the computer to power off 9.859
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.264
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.021
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.223
When the network is plugged 0.021
And Tor is ready 10.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.647
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.991
Given I shutdown Tails and wait for the computer to power off 8.167
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.417
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.416
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.217
When the network is plugged 0.019
And Tor is ready 10.505
Then the Upgrader considers the system as up-to-date 10.548
# 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.350
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.476
After features/support/hooks.rb:339 0.827
After features/support/hooks.rb:108 0.034
Tags: @product @automatic_upgrade
20.853
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.214
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 9.384
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.905
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.000