Project Number Date
test_Tails_ISO_devel 4450 16 Jun 2026, 13:30

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 13:4.718 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:15.753
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.044
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 14.323
When I start Tails from USB drive "old" with network unplugged 56.020
Then the boot device has safe access rights 3.365
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:339 3.877
After features/support/hooks.rb:108 0.026
Tags: @product
1:39.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 58.896
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 26.962
And I take note of which tps features are available 4.647
Then a Tails persistence partition exists on USB drive "old" 0.584
And I shutdown Tails and wait for the computer to power off 7.524
After features/support/hooks.rb:339 0.359
After features/support/hooks.rb:108 0.021
Tags: @product
1:47.506
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.211
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.608
Then Tails is running from USB drive "old" 0.332
And all tps features are active 6.007
When I write some files expected to persist 1.383
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.066
And I take note of which tps features are available 5.028
And I shutdown Tails and wait for the computer to power off 8.490
# 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.844
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.028
Tags: @product
2:19.094
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.012
And I log in to a new session 14.667
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.154
And I plug USB drive "to_upgrade" 2.857
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.384
Then the running Tails is installed on USB drive "to_upgrade" 16.704
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 2.300
After features/support/hooks.rb:108 0.000
Tags: @product
1:23.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.642
Then all tps features from the old Tails version are active 1.099
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.808
And the expected persistent files created with the old Tails version are present in the filesystem 1.333
And all persistent directories from the old Tails version have safe access rights 2.589
After features/support/hooks.rb:339 1.012
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
4:16.881
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.700
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.387
When the network is plugged 0.017
And Tor is ready 13.566
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.587
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.828
Given I shutdown Tails and wait for the computer to power off 10.658
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.628
Then Tails is running version 6.2~testoverlayfs 0.025
And all tps features are active 6.506
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.174
# 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.016
And Tor is ready 9.998
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.666
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.689
Given I shutdown Tails and wait for the computer to power off 7.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.974
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.900
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.017
And Tor is ready 11.866
Then the Upgrader considers the system as up-to-date 10.575
# 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 4.386
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:339 1.129
After features/support/hooks.rb:108 0.178
Tags: @product @automatic_upgrade
22.551
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.917
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.368
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.848
After features/support/hooks.rb:339 0.828
After features/support/hooks.rb:108 0.000