Project Number Date
test_Tails_ISO_devel 4452 16 Jun 2026, 17:49

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:3.551 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.273
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.111
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 13.216
When I start Tails from USB drive "old" with network unplugged 47.346
Then the boot device has safe access rights 2.726
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.220
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:339 1.277
After features/support/hooks.rb:108 0.017
Tags: @product
1:31.766
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.137
And I start Tails from USB drive "old" with network unplugged and I login 54.249
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 23.694
And I take note of which tps features are available 4.139
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 8.779
After features/support/hooks.rb:339 0.624
After features/support/hooks.rb:108 0.017
Tags: @product
1:42.978
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.150
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.578
Then Tails is running from USB drive "old" 0.254
And all tps features are active 5.060
When I write some files expected to persist 1.437
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.318
And all persistent directories from the old Tails version have safe access rights 2.389
And I take note of which tps features are available 4.539
And I shutdown Tails and wait for the computer to power off 8.420
# 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.649
After features/support/hooks.rb:339 0.401
After features/support/hooks.rb:108 0.025
Tags: @product
2:12.109
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.494
And I log in to a new session 12.367
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.819
And I plug USB drive "to_upgrade" 2.220
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.413
Then the running Tails is installed on USB drive "to_upgrade" 15.540
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.406
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.768
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.115
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.969
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.238
And the boot device has safe access rights 2.526
And the expected persistent files created with the old Tails version are present in the filesystem 1.080
And all persistent directories from the old Tails version have safe access rights 1.760
After features/support/hooks.rb:339 0.981
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:58.777
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.653
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.380
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.385
When the network is plugged 0.024
And Tor is ready 12.081
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.045
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.531
Given I shutdown Tails and wait for the computer to power off 9.821
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.206
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 5.488
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.146
# 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.197
When the network is plugged 0.013
And Tor is ready 10.802
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.360
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.108
Given I shutdown Tails and wait for the computer to power off 8.501
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.688
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 5.277
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.015
And Tor is ready 9.873
Then the Upgrader considers the system as up-to-date 10.612
# 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.763
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.340
After features/support/hooks.rb:339 0.800
After features/support/hooks.rb:108 0.046
Tags: @product @automatic_upgrade
19.877
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 7.634
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.015
And Tor is ready 10.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.860
After features/support/hooks.rb:339 0.879
After features/support/hooks.rb:108 0.000