Project Number Date
test_Tails_ISO_devel 4291 24 Mar 2026, 11:32

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:31.794 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:19.779
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.145
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.987
When I start Tails from USB drive "old" with network unplugged 1:0.938
Then the boot device has safe access rights 2.865
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 1.372
After features/support/hooks.rb:100 0.006
Tags: @product
1:31.563
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 55.624
Then Tails is running from USB drive "old" 0.320
And I create a persistent partition 25.751
And I take note of which tps features are available 0.789
Then a Tails persistence partition exists on USB drive "old" 0.628
And I shutdown Tails and wait for the computer to power off 8.372
After features/support/hooks.rb:331 0.375
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.319
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.215
When I write some files expected to persist 1.556
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.499
And all persistent directories from the old Tails version have safe access rights 2.069
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 8.261
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.818
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.298
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 8.132
And I log in to a new session 15.716
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.866
And I plug USB drive "to_upgrade" 2.295
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.685
Then the running Tails is installed on USB drive "to_upgrade" 16.315
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.097
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.582
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.808
Then all tps features from the old Tails version are active 1.064
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.020
And the expected persistent files created with the old Tails version are present in the filesystem 1.236
And all persistent directories from the old Tails version have safe access rights 2.077
After features/support/hooks.rb:331 0.764
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:45.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.624
And no SquashFS delta is installed 0.086
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.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.015
And Tor is ready 22.647
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.412
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.449
Given I shutdown Tails and wait for the computer to power off 20.649
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.759
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.492
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.212
When the network is plugged 0.016
And Tor is ready 20.819
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.380
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.122
Given I shutdown Tails and wait for the computer to power off 13.479
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.936
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.419
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.036
And Tor is ready 20.821
Then the Upgrader considers the system as up-to-date 0.150
# 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.490
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.400
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
50.315
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.492
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 41.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
After features/support/hooks.rb:331 0.976
After features/support/hooks.rb:100 0.000