Project Number Date
test_Tails_ISO_devel 4626 17 Sep 2026, 16:06

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:31.070 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:12.164
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 14.113
When I start Tails from USB drive "old" with network unplugged 53.953
Then the boot device has safe access rights 2.358
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.032
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.451
After features/support/hooks.rb:108 0.056
Tags: @product
1:26.391
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login 49.395
Then Tails is running from USB drive "old" 0.240
And I create a persistent partition 24.292
And I take note of which tps features are available 7.894
Then a Tails persistence partition exists on USB drive "old" 0.569
And I shutdown Tails and wait for the computer to power off 3.882
After features/support/hooks.rb:339 0.444
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.007
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.749
Then Tails is running from USB drive "old" 0.234
And all tps features are active 7.887
When I write some files expected to persist 1.222
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.212
And all persistent directories from the old Tails version have safe access rights 1.673
And I take note of which tps features are available 6.366
And I shutdown Tails and wait for the computer to power off 2.560
# 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.829
After features/support/hooks.rb:339 0.270
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.722
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.429
And I log in to a new session 11.591
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.696
And I plug USB drive "to_upgrade" 2.348
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.816
Then the running Tails is installed on USB drive "to_upgrade" 18.605
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.113
After features/support/hooks.rb:339 1.789
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.749
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.300
Then all tps features from the old Tails version are active 1.334
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.714
And the expected persistent files created with the old Tails version are present in the filesystem 1.194
And all persistent directories from the old Tails version have safe access rights 1.881
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.958
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.026
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.031
And Tor is ready 11.559
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.404
Given I shutdown Tails and wait for the computer to power off 5.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.414
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.812
And the file system changes introduced in version 6.2~testoverlayfs are present 0.187
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.179
When the network is plugged 0.030
And Tor is ready 10.391
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.508
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.486
Given I shutdown Tails and wait for the computer to power off 4.029
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.932
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.936
And the file system changes introduced in version 6.3~testoverlayfs are present 0.310
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.171
When the network is plugged 0.052
And Tor is ready 10.817
Then the Upgrader considers the system as up-to-date 0.148
# 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.748
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.468
After features/support/hooks.rb:339 0.840
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.077
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.816
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.028
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.355
After features/support/hooks.rb:339 0.622
After features/support/hooks.rb:108 0.000