Project Number Date
test_Tails_ISO_stable 6182 03 Mar 2026, 11:42

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:33.991 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.036
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 14.080
When I start Tails from USB drive "old" with network unplugged 53.164
Then the boot device has safe access rights 2.908
And Tails is running from USB drive "old" 0.290
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.246
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:331 3.555
After features/support/hooks.rb:100 0.071
Tags: @product
1:27.906
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 53.870
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 23.937
And I take note of which tps features are available 0.706
Then a Tails persistence partition exists on USB drive "old" 0.520
And I shutdown Tails and wait for the computer to power off 8.544
After features/support/hooks.rb:331 0.515
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.673
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.326
Then Tails is running from USB drive "old" 0.289
And all tps features are active 1.177
When I write some files expected to persist 1.318
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
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.268
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 7.955
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.425
After features/support/hooks.rb:331 0.159
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.691
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.594
And I log in to a new session 11.356
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.909
And I plug USB drive "to_upgrade" 2.269
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.624
Then the running Tails is installed on USB drive "to_upgrade" 16.663
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.309
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.211
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.114
Then all tps features from the old Tails version are active 0.964
And Tails is running from USB drive "to_upgrade" 0.254
And the boot device has safe access rights 2.582
And the expected persistent files created with the old Tails version are present in the filesystem 1.274
And all persistent directories from the old Tails version have safe access rights 1.927
After features/support/hooks.rb:331 0.666
After features/support/hooks.rb:100 0.019
4:32.227
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.436
And no SquashFS delta is installed 0.063
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.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.476
When the network is plugged 0.019
And Tor is ready 21.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.370
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.919
Given I shutdown Tails and wait for the computer to power off 15.084
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.206
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.316
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.215
When the network is plugged 0.017
And Tor is ready 20.245
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.433
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.984
Given I shutdown Tails and wait for the computer to power off 17.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.268
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.014
And Tor is ready 21.629
Then the Upgrader considers the system as up-to-date 0.090
# 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.233
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.336
After features/support/hooks.rb:331 0.778
After features/support/hooks.rb:100 0.011
26.244
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 with a persistent partition enabled and logged in 7.723
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 17.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.467
After features/support/hooks.rb:331 0.981
After features/support/hooks.rb:100 0.000