Project Number Date
test_Tails_ISO_devel 4562 20 Aug 2026, 11:20

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:38.865 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.578
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.126
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.848
When I start Tails from USB drive "old" with network unplugged 47.618
Then the boot device has safe access rights 2.266
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.533
After features/support/hooks.rb:108 0.008
Tags: @product
1:24.231
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 48.417
Then Tails is running from USB drive "old" 0.372
And I create a persistent partition 24.960
And I take note of which tps features are available 7.230
Then a Tails persistence partition exists on USB drive "old" 0.568
And I shutdown Tails and wait for the computer to power off 2.598
After features/support/hooks.rb:339 0.554
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.806
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.926
Then Tails is running from USB drive "old" 0.238
And all tps features are active 7.846
When I write some files expected to persist 1.194
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.271
And all persistent directories from the old Tails version have safe access rights 1.724
And I take note of which tps features are available 5.867
And I shutdown Tails and wait for the computer to power off 3.929
# 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.562
After features/support/hooks.rb:339 0.533
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.732
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.268
And I log in to a new session 11.203
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.647
And I plug USB drive "to_upgrade" 2.181
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.873
Then the running Tails is installed on USB drive "to_upgrade" 19.283
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:339 0.661
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.287
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.057
Then all tps features from the old Tails version are active 1.035
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.281
And the expected persistent files created with the old Tails version are present in the filesystem 1.022
And all persistent directories from the old Tails version have safe access rights 1.596
After features/support/hooks.rb:339 0.952
After features/support/hooks.rb:108 0.057
Tags: @product @automatic_upgrade
3:47.576
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.638
And no SquashFS delta is installed 0.091
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.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.388
When the network is plugged 0.028
And Tor is ready 13.683
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.788
Given I shutdown Tails and wait for the computer to power off 5.413
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.560
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.679
And the file system changes introduced in version 6.2~testoverlayfs are present 0.241
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.149
# 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.203
When the network is plugged 0.034
And Tor is ready 11.380
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.311
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.886
Given I shutdown Tails and wait for the computer to power off 4.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.319
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.450
And the file system changes introduced in version 6.3~testoverlayfs are present 0.321
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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.026
And Tor is ready 10.293
Then the Upgrader considers the system as up-to-date 10.383
# 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.576
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.405
After features/support/hooks.rb:339 0.900
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
19.652
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.267
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 8.802
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.228
After features/support/hooks.rb:339 0.595
After features/support/hooks.rb:108 0.000