Project Number Date
test_Tails_ISO_21757-update-electrum 1 31 Aug 2026, 14:24

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:53.740 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:11.276
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.137
When I start Tails from USB drive "old" with network unplugged 54.207
Then the boot device has safe access rights 2.145
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.442
After features/support/hooks.rb:108 0.005
Tags: @product
1:19.209
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 46.961
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 22.729
And I take note of which tps features are available 6.054
Then a Tails persistence partition exists on USB drive "old" 0.484
And I shutdown Tails and wait for the computer to power off 2.656
After features/support/hooks.rb:339 0.182
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.181
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.723
Then Tails is running from USB drive "old" 0.183
And all tps features are active 7.025
When I write some files expected to persist 0.998
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.110
And all persistence configuration files have safe access rights 0.197
And all persistent directories from the old Tails version have safe access rights 1.504
And I take note of which tps features are available 5.714
And I shutdown Tails and wait for the computer to power off 2.512
# 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.109
After features/support/hooks.rb:339 0.086
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.890
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 without a persistent partition and stopped at Tails Greeter's login screen 8.048
And I log in to a new session 11.703
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.631
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.120
Then the running Tails is installed on USB drive "to_upgrade" 17.847
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 3.912
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.771
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.095
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.251
Then all tps features from the old Tails version are active 1.048
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 1.958
And the expected persistent files created with the old Tails version are present in the filesystem 0.898
And all persistent directories from the old Tails version have safe access rights 1.283
After features/support/hooks.rb:339 0.916
After features/support/hooks.rb:108 0.004
Tags: @product @automatic_upgrade
3:19.227
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 7.943
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.101
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.182
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.324
When the network is plugged 0.031
And Tor is ready 11.895
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.089
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.700
Given I shutdown Tails and wait for the computer to power off 5.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.602
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.439
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.079
# 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.138
When the network is plugged 0.034
And Tor is ready 10.011
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.453
Given I shutdown Tails and wait for the computer to power off 2.541
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.946
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.219
And the file system changes introduced in version 6.3~testoverlayfs are present 0.313
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.025
And Tor is ready 10.048
Then the Upgrader considers the system as up-to-date 0.119
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.329
After features/support/hooks.rb:339 0.572
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
18.183
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 7.828
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.189
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.124
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 8.014
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.965
After features/support/hooks.rb:339 0.921
After features/support/hooks.rb:108 0.000