Project Number Date
test_Tails_ISO_devel 4418 27 May 2026, 13:05

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 12:29.054 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:23.143
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.673
When I start Tails from USB drive "old" with network unplugged 1:3.861
Then the boot device has safe access rights 2.860
And Tails is running from USB drive "old" 0.206
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:335 3.446
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.272
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 56.627
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 26.833
And I take note of which tps features are available 0.442
Then a Tails persistence partition exists on USB drive "old" 0.717
And I shutdown Tails and wait for the computer to power off 7.227
After features/support/hooks.rb:335 0.613
After features/support/hooks.rb:104 0.009
Tags: @product
1:35.039
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.200
Then Tails is running from USB drive "old" 0.247
And all tps features are active 1.863
When I write some files expected to persist 1.837
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.558
And I take note of which tps features are available 0.245
And I shutdown Tails and wait for the computer to power off 4.367
# 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" 15.055
After features/support/hooks.rb:335 0.340
After features/support/hooks.rb:104 0.010
Tags: @product
2:19.110
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.131
And I log in to a new session 15.661
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.864
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.793
Then the running Tails is installed on USB drive "to_upgrade" 18.070
And I unplug USB drive "to_upgrade" 0.167
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:335 2.255
After features/support/hooks.rb:104 0.000
Tags: @product
1:19.331
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.664
Then all tps features from the old Tails version are active 1.046
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 3.591
And the expected persistent files created with the old Tails version are present in the filesystem 1.324
And all persistent directories from the old Tails version have safe access rights 2.383
After features/support/hooks.rb:335 1.035
After features/support/hooks.rb:104 0.008
3:57.783
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 with a persistent partition enabled and logged in 8.708
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.018
And Tor is ready 14.548
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.744
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.179
Given I shutdown Tails and wait for the computer to power off 7.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.485
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.794
And the file system changes introduced in version 6.2~testoverlayfs are present 0.330
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.263
When the network is plugged 0.042
And Tor is ready 10.431
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.453
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.458
Given I shutdown Tails and wait for the computer to power off 8.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.783
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.446
And the file system changes introduced in version 6.3~testoverlayfs are present 0.405
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.408
When the network is plugged 0.022
And Tor is ready 10.560
Then the Upgrader considers the system as up-to-date 10.553
# 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.407
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.392
After features/support/hooks.rb:335 0.900
After features/support/hooks.rb:104 0.015
22.373
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 with a persistent partition enabled and logged in 8.291
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.082
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.337
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.338
After features/support/hooks.rb:335 0.879
After features/support/hooks.rb:104 0.000