Project Number Date
test_Tails_ISO_stable 6607 26 Aug 2026, 12:42

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:57.607 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.536
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.495
And I create a 7200 MiB disk named "old" 0.069
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 14.769
When I start Tails from USB drive "old" with network unplugged 45.813
Then the boot device has safe access rights 2.744
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.185
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.090
After features/support/hooks.rb:108 0.007
Tags: @product
1:25.544
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 49.404
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.705
And I take note of which tps features are available 6.390
Then a Tails persistence partition exists on USB drive "old" 0.843
And I shutdown Tails and wait for the computer to power off 3.866
After features/support/hooks.rb:339 0.325
After features/support/hooks.rb:108 0.007
Tags: @product
1:39.633
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.418
Then Tails is running from USB drive "old" 0.267
And all tps features are active 7.864
When I write some files expected to persist 1.111
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.650
And I take note of which tps features are available 6.759
And I shutdown Tails and wait for the computer to power off 4.100
# 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.918
After features/support/hooks.rb:339 0.248
After features/support/hooks.rb:108 0.006
Tags: @product
2:17.525
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 9.930
And I log in to a new session 11.766
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.662
And I plug USB drive "to_upgrade" 2.285
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.514
Then the running Tails is installed on USB drive "to_upgrade" 20.098
And I unplug USB drive "to_upgrade" 0.128
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 3.662
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.918
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.106
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.894
Then all tps features from the old Tails version are active 1.213
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.547
And the expected persistent files created with the old Tails version are present in the filesystem 1.172
And all persistent directories from the old Tails version have safe access rights 1.703
After features/support/hooks.rb:339 0.722
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:55.831
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.338
And no SquashFS delta is installed 0.137
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.172
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.293
When the network is plugged 0.027
And Tor is ready 13.216
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.736
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.924
Given I shutdown Tails and wait for the computer to power off 5.340
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.616
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 9.041
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.226
When the network is plugged 0.031
And Tor is ready 10.543
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.639
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.453
Given I shutdown Tails and wait for the computer to power off 4.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.935
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.555
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.026
And Tor is ready 9.477
Then the Upgrader considers the system as up-to-date 10.466
# 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.661
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 0.972
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.617
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.420
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
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.033
And Tor is ready 9.330
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.521
After features/support/hooks.rb:339 0.567
After features/support/hooks.rb:108 0.000