Project Number Date
test_Tails_ISO_devel 4410 22 May 2026, 11:20

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:46.816 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.866
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.065
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.777
When I start Tails from USB drive "old" with network unplugged 57.555
Then the boot device has safe access rights 2.756
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:335 1.380
After features/support/hooks.rb:104 0.006
Tags: @product
1:31.454
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 56.672
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 24.922
And I take note of which tps features are available 0.437
Then a Tails persistence partition exists on USB drive "old" 0.664
And I shutdown Tails and wait for the computer to power off 8.476
After features/support/hooks.rb:335 0.421
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.790
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.835
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.219
When I write some files expected to persist 1.301
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.341
And all persistent directories from the old Tails version have safe access rights 1.944
And I take note of which tps features are available 0.205
And I shutdown Tails and wait for the computer to power off 8.119
# 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.345
After features/support/hooks.rb:335 0.572
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.685
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.080
And I log in to a new session 12.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.911
And I plug USB drive "to_upgrade" 2.247
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.015
Then the running Tails is installed on USB drive "to_upgrade" 15.436
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:335 2.375
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.283
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.274
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 2.975
And the expected persistent files created with the old Tails version are present in the filesystem 1.325
And all persistent directories from the old Tails version have safe access rights 2.261
After features/support/hooks.rb:335 1.017
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:44.984
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.956
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.024
And Tor is ready 13.724
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.494
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.512
Given I shutdown Tails and wait for the computer to power off 9.672
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.904
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.361
And the file system changes introduced in version 6.2~testoverlayfs are present 0.256
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.154
# 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.240
When the network is plugged 0.022
And Tor is ready 10.565
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.737
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.572
Given I shutdown Tails and wait for the computer to power off 4.184
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.161
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.341
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.176
When the network is plugged 0.017
And Tor is ready 10.109
Then the Upgrader considers the system as up-to-date 10.585
# 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.139
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.354
After features/support/hooks.rb:335 0.959
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
19.751
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.935
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 9.712
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.799
After features/support/hooks.rb:335 0.995
After features/support/hooks.rb:104 0.000