Project Number Date
test_Tails_ISO_devel 4394 13 May 2026, 11:07

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:1.005 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.657
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.036
When I start Tails from USB drive "old" with network unplugged 40.311
Then the boot device has safe access rights 2.509
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:335 3.472
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.425
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 52.319
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 24.746
And I take note of which tps features are available 0.354
Then a Tails persistence partition exists on USB drive "old" 0.576
And I shutdown Tails and wait for the computer to power off 8.130
After features/support/hooks.rb:335 0.446
After features/support/hooks.rb:104 0.006
Tags: @product
1:23.633
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.678
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.119
When I write some files expected to persist 1.150
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.150
And all persistence configuration files have safe access rights 0.262
And all persistent directories from the old Tails version have safe access rights 1.823
And I take note of which tps features are available 0.143
And I shutdown Tails and wait for the computer to power off 8.020
# 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.999
After features/support/hooks.rb:335 0.185
After features/support/hooks.rb:104 0.006
Tags: @product
2:9.330
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.525
And I log in to a new session 11.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.648
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.844
Then the running Tails is installed on USB drive "to_upgrade" 15.098
And I unplug USB drive "to_upgrade" 0.144
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:335 2.106
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.619
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.942
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.578
And the expected persistent files created with the old Tails version are present in the filesystem 0.988
And all persistent directories from the old Tails version have safe access rights 1.802
After features/support/hooks.rb:335 0.595
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:36.699
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.074
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.281
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.013
And Tor is ready 13.320
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.077
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.550
Given I shutdown Tails and wait for the computer to power off 9.377
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.505
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 0.991
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.194
When the network is plugged 0.019
And Tor is ready 10.066
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.168
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.668
Given I shutdown Tails and wait for the computer to power off 7.904
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.256
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.124
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.018
And Tor is ready 11.272
Then the Upgrader considers the system as up-to-date 10.503
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.401
After features/support/hooks.rb:335 0.660
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.639
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.011
After features/support/hooks.rb:335 0.539
After features/support/hooks.rb:104 0.000