Project Number Date
test_Tails_ISO_devel 4549 14 Aug 2026, 11:16

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:58.168 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
54.269
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.377
When I start Tails from USB drive "old" with network unplugged 37.361
Then the boot device has safe access rights 1.760
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.043
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.791
After features/support/hooks.rb:108 0.027
Tags: @product
1:21.419
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 47.385
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 22.879
And I take note of which tps features are available 6.207
Then a Tails persistence partition exists on USB drive "old" 0.503
And I shutdown Tails and wait for the computer to power off 4.092
After features/support/hooks.rb:339 0.421
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.095
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.312
Then Tails is running from USB drive "old" 0.296
And all tps features are active 9.012
When I write some files expected to persist 1.086
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.105
And all persistence configuration files have safe access rights 0.257
And all persistent directories from the old Tails version have safe access rights 1.461
And I take note of which tps features are available 5.694
And I shutdown Tails and wait for the computer to power off 2.572
# 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" 11.213
After features/support/hooks.rb:339 0.173
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.208
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.461
And I log in to a new session 11.113
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.655
And I plug USB drive "to_upgrade" 2.176
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.249
Then the running Tails is installed on USB drive "to_upgrade" 19.316
And I unplug USB drive "to_upgrade" 0.115
And I unplug USB drive "__internal" 0.120
After features/support/hooks.rb:339 1.919
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.834
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.586
Then all tps features from the old Tails version are active 1.004
And Tails is running from USB drive "to_upgrade" 0.178
And the boot device has safe access rights 1.801
And the expected persistent files created with the old Tails version are present in the filesystem 0.784
And all persistent directories from the old Tails version have safe access rights 1.382
After features/support/hooks.rb:339 0.819
After features/support/hooks.rb:108 0.012
3:27.839
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.146
And no SquashFS delta is installed 0.081
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
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.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.351
When the network is plugged 0.028
And Tor is ready 11.926
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.536
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.655
Given I shutdown Tails and wait for the computer to power off 5.477
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.141
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.050
And the file system changes introduced in version 6.2~testoverlayfs are present 0.170
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.089
# 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.158
When the network is plugged 0.025
And Tor is ready 10.330
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.479
Given I shutdown Tails and wait for the computer to power off 2.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.712
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.914
And the file system changes introduced in version 6.3~testoverlayfs are present 0.341
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.164
When the network is plugged 0.032
And Tor is ready 10.568
Then the Upgrader considers the system as up-to-date 0.207
# 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.519
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:339 1.023
After features/support/hooks.rb:108 0.053
20.500
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.047
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
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.031
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.474
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.642
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.000