Project Number Date
test_Tails_ISO_devel 4320 05 Apr 2026, 11:33

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 13:50.981 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:14.691
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.101
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 15.073
When I start Tails from USB drive "old" with network unplugged 54.821
Then the boot device has safe access rights 2.878
And Tails is running from USB drive "old" 0.272
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.243
And I unplug USB drive "old" 0.160
After features/support/hooks.rb:331 3.497
After features/support/hooks.rb:100 0.007
Tags: @product
1:37.326
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 1:1.781
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.582
And I take note of which tps features are available 0.796
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 8.255
After features/support/hooks.rb:331 0.608
After features/support/hooks.rb:100 0.009
Tags: @product
1:32.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.371
Then Tails is running from USB drive "old" 0.304
And all tps features are active 1.181
When I write some files expected to persist 1.194
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.434
And all persistent directories from the old Tails version have safe access rights 2.064
And I take note of which tps features are available 0.174
And I shutdown Tails and wait for the computer to power off 8.638
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.902
After features/support/hooks.rb:331 0.276
After features/support/hooks.rb:100 0.013
Tags: @product
2:23.481
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.336
And I log in to a new session 20.022
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.149
And I plug USB drive "to_upgrade" 2.610
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.922
Then the running Tails is installed on USB drive "to_upgrade" 17.014
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.219
After features/support/hooks.rb:331 4.843
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.127
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.565
Then all tps features from the old Tails version are active 1.146
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.254
And the expected persistent files created with the old Tails version are present in the filesystem 1.367
And all persistent directories from the old Tails version have safe access rights 2.342
After features/support/hooks.rb:331 0.788
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:53.235
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.692
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.529
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.408
When the network is plugged 0.018
And Tor is ready 28.437
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.499
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.294
Given I shutdown Tails and wait for the computer to power off 19.643
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.704
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.527
And the file system changes introduced in version 6.2~testoverlayfs are present 0.268
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.251
When the network is plugged 0.015
And Tor is ready 22.292
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.402
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.392
Given I shutdown Tails and wait for the computer to power off 12.656
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.458
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.266
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.017
And Tor is ready 21.590
Then the Upgrader considers the system as up-to-date 0.140
# 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.937
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 0.950
After features/support/hooks.rb:100 0.030
Tags: @product @automatic_upgrade
51.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.236
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.266
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 41.546
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.369
After features/support/hooks.rb:331 0.776
After features/support/hooks.rb:100 0.000