Project Number Date
test_Tails_ISO_devel 4665 08 Oct 2026, 11:16

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:0.493 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
56.575
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.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.345
When I start Tails from USB drive "old" with network unplugged 39.737
Then the boot device has safe access rights 1.834
And Tails is running from USB drive "old" 0.163
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.162
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.489
After features/support/hooks.rb:108 0.006
Tags: @product
1:18.331
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 46.690
Then Tails is running from USB drive "old" 0.197
And I create a persistent partition 22.326
And I take note of which tps features are available 5.998
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 2.539
After features/support/hooks.rb:339 0.521
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.889
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.506
Then Tails is running from USB drive "old" 0.216
And all tps features are active 6.637
When I write some files expected to persist 0.894
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.120
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 1.481
And I take note of which tps features are available 5.899
And I shutdown Tails and wait for the computer to power off 2.525
# 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.095
After features/support/hooks.rb:339 0.403
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.349
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.011
And I log in to a new session 11.521
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.746
And I plug USB drive "to_upgrade" 2.174
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.456
Then the running Tails is installed on USB drive "to_upgrade" 17.198
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 1.554
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.795
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.983
Then all tps features from the old Tails version are active 1.047
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 1.970
And the expected persistent files created with the old Tails version are present in the filesystem 0.970
And all persistent directories from the old Tails version have safe access rights 1.508
After features/support/hooks.rb:339 0.835
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:20.258
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.260
And no SquashFS delta is installed 0.059
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.074
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.155
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.023
And Tor is ready 10.705
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.813
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.820
Given I shutdown Tails and wait for the computer to power off 5.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.501
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.111
And the file system changes introduced in version 6.2~testoverlayfs are present 0.185
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.178
# 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.168
When the network is plugged 0.024
And Tor is ready 10.132
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.292
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.468
Given I shutdown Tails and wait for the computer to power off 2.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.081
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.728
And the file system changes introduced in version 6.3~testoverlayfs are present 0.262
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.146
When the network is plugged 0.032
And Tor is ready 9.884
Then the Upgrader considers the system as up-to-date 0.083
# 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.099
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
43.293
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 33.773
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 7.844
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.370
After features/support/hooks.rb:339 0.902
After features/support/hooks.rb:108 0.000