Project Number Date
test_Tails_ISO_stable 5954 15 Nov 2025, 02:50

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 16:32.730 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
2:4.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 31.925
When I start Tails from USB drive "old" with network unplugged 1:27.280
Then the boot device has safe access rights 2.818
And Tails is running from USB drive "old" 0.310
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:331 3.842
After features/support/hooks.rb:100 0.012
Tags: @product
2:10.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:25.058
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 33.083
And I take note of which tps features are available 1.173
Then a Tails persistence partition exists on USB drive "old" 6.460
And I shutdown Tails and wait for the computer to power off 4.602
After features/support/hooks.rb:331 0.663
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.002
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.259
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.275
Then Tails is running from USB drive "old" 0.313
And all tps features are active 1.883
When I write some files expected to persist 1.489
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.408
And all persistent directories from the old Tails version have safe access rights 2.151
And I take note of which tps features are available 0.452
And I shutdown Tails and wait for the computer to power off 7.543
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.031
After features/support/hooks.rb:331 0.478
After features/support/hooks.rb:100 0.024
Tags: @product
2:33.664
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 without a persistent partition and stopped at Tails Greeter's login screen 11.807
And I log in to a new session 16.343
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.113
And I plug USB drive "to_upgrade" 2.347
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.080
Then the running Tails is installed on USB drive "to_upgrade" 20.606
And I unplug USB drive "to_upgrade" 0.184
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 3.817
After features/support/hooks.rb:100 0.000
Tags: @product
1:43.302
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:34.992
Then all tps features from the old Tails version are active 1.395
And Tails is running from USB drive "to_upgrade" 0.294
And the boot device has safe access rights 2.934
And the expected persistent files created with the old Tails version are present in the filesystem 1.260
And all persistent directories from the old Tails version have safe access rights 2.263
After features/support/hooks.rb:331 1.142
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
5:24.749
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 15.571
And no SquashFS delta is installed 0.161
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.053
And Tor is ready 13.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.742
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.086
Given I shutdown Tails and wait for the computer to power off 11.134
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.365
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.071
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.164
# 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.243
When the network is plugged 0.046
And Tor is ready 10.571
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.711
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 16.201
Given I shutdown Tails and wait for the computer to power off 7.812
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.912
Then Tails is running version 6.3~testoverlayfs 0.053
And all tps features are active 1.973
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.060
And Tor is ready 11.677
Then the Upgrader considers the system as up-to-date 0.292
# 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 6.162
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.475
After features/support/hooks.rb:331 10.359
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
26.046
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.045
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.371
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.338
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 11.570
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.600
After features/support/hooks.rb:331 1.076
After features/support/hooks.rb:100 0.000