Project Number Date
test_Tails_ISO_stable 6231 25 Mar 2026, 12:59

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:9.098 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:12.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.703
When I start Tails from USB drive "old" with network unplugged 52.925
Then the boot device has safe access rights 3.141
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.570
After features/support/hooks.rb:100 0.025
Tags: @product
1:34.000
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 59.122
Then Tails is running from USB drive "old" 0.344
And I create a persistent partition 28.170
And I take note of which tps features are available 1.008
Then a Tails persistence partition exists on USB drive "old" 0.765
And I shutdown Tails and wait for the computer to power off 4.509
After features/support/hooks.rb:331 0.433
After features/support/hooks.rb:100 0.012
Tags: @product
1:34.520
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.067
Then Tails is running from USB drive "old" 0.314
And all tps features are active 1.194
When I write some files expected to persist 1.445
# 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.597
And all persistent directories from the old Tails version have safe access rights 2.570
And I take note of which tps features are available 0.195
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" 13.613
After features/support/hooks.rb:331 0.326
After features/support/hooks.rb:100 0.011
Tags: @product
2:16.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.177
And I log in to a new session 13.761
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.859
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.096
Then the running Tails is installed on USB drive "to_upgrade" 18.003
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.890
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.954
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.065
Then all tps features from the old Tails version are active 1.189
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.024
And the expected persistent files created with the old Tails version are present in the filesystem 1.665
And all persistent directories from the old Tails version have safe access rights 2.614
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.008
4:45.818
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 9.559
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.377
When the network is plugged 0.024
And Tor is ready 22.754
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.453
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.659
Given I shutdown Tails and wait for the computer to power off 20.452
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.953
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.572
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.244
When the network is plugged 0.022
And Tor is ready 20.860
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.523
Given I shutdown Tails and wait for the computer to power off 12.763
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.736
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.485
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.015
And Tor is ready 21.463
Then the Upgrader considers the system as up-to-date 0.145
# 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 5.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.051
26.814
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.968
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.045
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.443
After features/support/hooks.rb:331 0.960
After features/support/hooks.rb:100 0.000