Project Number Date
test_Tails_ISO_stable 6061 14 Jan 2026, 13: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 12:13.163 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:21.086
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.251
When I start Tails from USB drive "old" with network unplugged 1:1.214
Then the boot device has safe access rights 3.694
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.091
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.736
After features/support/hooks.rb:100 0.007
Tags: @product
1:36.729
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 58.961
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 27.619
And I take note of which tps features are available 1.151
Then a Tails persistence partition exists on USB drive "old" 0.732
And I shutdown Tails and wait for the computer to power off 7.836
After features/support/hooks.rb:331 0.180
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.406
Then Tails is running from USB drive "old" 0.242
And all tps features are active 1.154
When I write some files expected to persist 1.406
# 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.324
And all persistent directories from the old Tails version have safe access rights 1.934
And I take note of which tps features are available 0.273
And I shutdown Tails and wait for the computer to power off 8.493
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.456
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.412
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 9.432
And I log in to a new session 11.533
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.001
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.647
Then the running Tails is installed on USB drive "to_upgrade" 17.108
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.136
After features/support/hooks.rb:331 3.782
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.260
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.311
Then all tps features from the old Tails version are active 1.086
And Tails is running from USB drive "to_upgrade" 0.334
And the boot device has safe access rights 3.122
And the expected persistent files created with the old Tails version are present in the filesystem 1.307
And all persistent directories from the old Tails version have safe access rights 2.028
After features/support/hooks.rb:331 0.580
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
3:53.604
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 with a persistent partition enabled and logged in 8.056
And no SquashFS delta is installed 0.123
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.017
And Tor is ready 13.507
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.289
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.687
Given I shutdown Tails and wait for the computer to power off 10.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.474
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.326
# 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.340
When the network is plugged 0.057
And Tor is ready 11.155
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.737
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.649
Given I shutdown Tails and wait for the computer to power off 8.464
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.305
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.239
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.016
And Tor is ready 12.032
Then the Upgrader considers the system as up-to-date 10.653
# 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.376
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.537
After features/support/hooks.rb:331 0.999
After features/support/hooks.rb:100 0.044
Tags: @product @automatic_upgrade
21.138
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.167
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.912
After features/support/hooks.rb:331 0.704
After features/support/hooks.rb:100 0.000