Project Number Date
test_Tails_ISO_stable 6578 13 Aug 2026, 18: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:14.619 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
57.216
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.234
When I start Tails from USB drive "old" with network unplugged 39.012
Then the boot device has safe access rights 2.271
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.139
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.565
After features/support/hooks.rb:108 0.006
Tags: @product
1:22.885
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 49.381
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 23.420
And I take note of which tps features are available 6.632
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 2.598
After features/support/hooks.rb:339 0.446
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.893
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.581
Then Tails is running from USB drive "old" 0.425
And all tps features are active 8.457
When I write some files expected to persist 1.013
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.127
And all persistence configuration files have safe access rights 0.240
And all persistent directories from the old Tails version have safe access rights 1.669
And I take note of which tps features are available 6.604
And I shutdown Tails and wait for the computer to power off 2.723
# 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.953
After features/support/hooks.rb:339 0.443
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.996
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 without a persistent partition and stopped at Tails Greeter's login screen 8.270
And I log in to a new session 11.645
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.613
And I plug USB drive "to_upgrade" 2.311
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.894
Then the running Tails is installed on USB drive "to_upgrade" 18.998
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 1.894
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.956
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.121
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.242
Then all tps features from the old Tails version are active 1.018
And Tails is running from USB drive "to_upgrade" 0.206
And the boot device has safe access rights 2.607
And the expected persistent files created with the old Tails version are present in the filesystem 1.107
And all persistent directories from the old Tails version have safe access rights 1.652
After features/support/hooks.rb:339 0.736
After features/support/hooks.rb:108 0.061
Tags: @product @automatic_upgrade
3:35.884
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.603
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.029
And Tor is ready 11.539
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.356
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.055
Given I shutdown Tails and wait for the computer to power off 5.349
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.226
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 8.711
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
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.096
# 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.141
When the network is plugged 0.032
And Tor is ready 10.695
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.194
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.109
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.279
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.690
And the file system changes introduced in version 6.3~testoverlayfs are present 0.287
And only the 6.3~testoverlayfs SquashFS delta is installed 0.030
# 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.074
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.047
And Tor is ready 10.115
Then the Upgrader considers the system as up-to-date 0.108
# 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.106
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.267
After features/support/hooks.rb:339 1.003
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.785
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 7.970
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 9.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.905
After features/support/hooks.rb:339 0.900
After features/support/hooks.rb:108 0.000