Project Number Date
test_Tails_ISO_stable 6073 16 Jan 2026, 11:22

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:37.068 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:17.104
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.497
When I start Tails from USB drive "old" with network unplugged 58.592
Then the boot device has safe access rights 3.125
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.086
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.212
After features/support/hooks.rb:331 3.702
After features/support/hooks.rb:100 0.017
Tags: @product
1:25.003
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.178
And I start Tails from USB drive "old" with network unplugged and I login 54.531
Then Tails is running from USB drive "old" 0.450
And I create a persistent partition 24.196
And I take note of which tps features are available 0.738
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 4.331
After features/support/hooks.rb:331 0.422
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.642
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.332
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.087
When I write some files expected to persist 1.264
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 1.970
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.016
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.021
After features/support/hooks.rb:331 0.188
After features/support/hooks.rb:100 0.006
Tags: @product
2:13.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.963
And I log in to a new session 10.777
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.076
And I plug USB drive "to_upgrade" 2.305
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.146
Then the running Tails is installed on USB drive "to_upgrade" 17.001
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 3.580
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.536
Then all tps features from the old Tails version are active 1.440
And Tails is running from USB drive "to_upgrade" 0.309
And the boot device has safe access rights 2.733
And the expected persistent files created with the old Tails version are present in the filesystem 1.080
And all persistent directories from the old Tails version have safe access rights 2.069
After features/support/hooks.rb:331 1.142
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:42.778
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.266
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.366
When the network is plugged 0.017
And Tor is ready 12.782
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.053
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.991
Given I shutdown Tails and wait for the computer to power off 9.892
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.488
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.182
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
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.160
# 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.223
When the network is plugged 0.019
And Tor is ready 10.583
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.682
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.497
Given I shutdown Tails and wait for the computer to power off 7.971
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.285
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.099
And the file system changes introduced in version 6.3~testoverlayfs are present 0.396
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.019
And Tor is ready 10.225
Then the Upgrader considers the system as up-to-date 10.587
# 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.306
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 0.638
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
19.742
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 7.451
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.171
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.858
After features/support/hooks.rb:331 1.093
After features/support/hooks.rb:100 0.000