Project Number Date
test_Tails_ISO_stable 6020 23 Dec 2025, 11:02

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 10:49.870 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:3.790
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.432
When I start Tails from USB drive "old" with network unplugged 46.027
Then the boot device has safe access rights 2.570
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.803
After features/support/hooks.rb:100 0.032
Tags: @product
1:23.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 50.221
Then Tails is running from USB drive "old" 0.254
And I create a persistent partition 23.575
And I take note of which tps features are available 0.669
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 7.814
After features/support/hooks.rb:331 0.216
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.123
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.598
Then Tails is running from USB drive "old" 0.240
And all tps features are active 1.017
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 1.843
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 7.920
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.512
After features/support/hooks.rb:331 0.170
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.905
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.309
And I log in to a new session 11.504
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.842
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.872
Then the running Tails is installed on USB drive "to_upgrade" 14.875
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 3.720
After features/support/hooks.rb:100 0.000
Tags: @product
1:3.537
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 57.077
Then all tps features from the old Tails version are active 0.864
And Tails is running from USB drive "to_upgrade" 0.245
And the boot device has safe access rights 2.524
And the expected persistent files created with the old Tails version are present in the filesystem 1.073
And all persistent directories from the old Tails version have safe access rights 1.698
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:26.754
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 8.304
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.015
And Tor is ready 12.130
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.126
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.346
Given I shutdown Tails and wait for the computer to power off 5.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.202
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.015
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.166
# 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.207
When the network is plugged 0.050
And Tor is ready 12.186
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.819
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.934
Given I shutdown Tails and wait for the computer to power off 7.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.523
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.034
And the file system changes introduced in version 6.3~testoverlayfs are present 0.402
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.139
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.013
And Tor is ready 10.858
Then the Upgrader considers the system as up-to-date 10.523
# 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 3.835
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.357
After features/support/hooks.rb:331 1.086
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
20.663
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.622
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.204
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.060
After features/support/hooks.rb:331 0.648
After features/support/hooks.rb:100 0.000