Project Number Date
test_Tails_ISO_devel 4438 09 Jun 2026, 07:58

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:51.982 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:7.246
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.164
When I start Tails from USB drive "old" with network unplugged 48.146
Then the boot device has safe access rights 3.017
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.281
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:335 1.707
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.325
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 56.001
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 25.742
And I take note of which tps features are available 0.374
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 8.224
After features/support/hooks.rb:335 0.542
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.012
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.312
Then Tails is running from USB drive "old" 0.389
And all tps features are active 1.555
When I write some files expected to persist 1.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.176
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 2.093
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 6.887
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.691
After features/support/hooks.rb:335 0.351
After features/support/hooks.rb:104 0.006
Tags: @product
2:14.232
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.218
And I log in to a new session 13.756
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.939
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.733
Then the running Tails is installed on USB drive "to_upgrade" 15.924
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:335 2.216
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.604
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.018
Given a computer 0.150
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.097
Then all tps features from the old Tails version are active 1.132
And Tails is running from USB drive "to_upgrade" 0.200
And the boot device has safe access rights 2.427
And the expected persistent files created with the old Tails version are present in the filesystem 1.269
And all persistent directories from the old Tails version have safe access rights 2.326
After features/support/hooks.rb:335 0.748
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
3:52.848
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.843
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.265
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.016
And Tor is ready 13.878
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.245
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.838
Given I shutdown Tails and wait for the computer to power off 9.516
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.686
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 1.307
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.247
When the network is plugged 0.016
And Tor is ready 12.064
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.742
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.966
Given I shutdown Tails and wait for the computer to power off 4.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.789
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.349
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.089
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.025
And Tor is ready 11.705
Then the Upgrader considers the system as up-to-date 10.597
# 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.013
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.435
After features/support/hooks.rb:335 0.636
After features/support/hooks.rb:104 0.013
Tags: @product @automatic_upgrade
21.711
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.248
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.919
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.201
After features/support/hooks.rb:335 1.068
After features/support/hooks.rb:104 0.000