Project Number Date
test_Tails_ISO_devel 4431 04 Jun 2026, 15:57

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.745 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:2.786
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 14.085
When I start Tails from USB drive "old" with network unplugged 44.026
Then the boot device has safe access rights 2.907
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:335 3.807
After features/support/hooks.rb:104 0.009
Tags: @product
1:31.268
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 55.252
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 26.318
And I take note of which tps features are available 0.318
Then a Tails persistence partition exists on USB drive "old" 0.478
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.524
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.508
Then Tails is running from USB drive "old" 0.252
And all tps features are active 1.296
When I write some files expected to persist 1.412
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.321
And all persistent directories from the old Tails version have safe access rights 1.967
And I take note of which tps features are available 0.235
And I shutdown Tails and wait for the computer to power off 4.125
# 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.166
After features/support/hooks.rb:335 0.303
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.113
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 without a persistent partition and stopped at Tails Greeter's login screen 7.936
And I log in to a new session 12.247
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.864
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.306
Then the running Tails is installed on USB drive "to_upgrade" 16.214
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.157
After features/support/hooks.rb:335 2.467
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.502
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.057
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.037
Then all tps features from the old Tails version are active 0.954
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.713
And the expected persistent files created with the old Tails version are present in the filesystem 1.048
And all persistent directories from the old Tails version have safe access rights 2.441
After features/support/hooks.rb:335 0.814
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:50.619
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.443
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.020
And Tor is ready 13.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.790
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.102
Given I shutdown Tails and wait for the computer to power off 11.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.454
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.136
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.225
When the network is plugged 0.017
And Tor is ready 12.382
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.973
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.510
Given I shutdown Tails and wait for the computer to power off 8.150
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.044
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.388
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.021
And Tor is ready 11.032
Then the Upgrader considers the system as up-to-date 10.555
# 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.258
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:335 0.857
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.931
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 7.889
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 10.024
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.527
After features/support/hooks.rb:335 0.854
After features/support/hooks.rb:104 0.000