Project Number Date
test_Tails_ISO_devel 4538 10 Aug 2026, 11:46

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:43.173 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:4.830
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.981
When I start Tails from USB drive "old" with network unplugged 46.736
Then the boot device has safe access rights 2.360
And Tails is running from USB drive "old" 0.200
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 1.128
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.498
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 51.465
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 24.007
And I take note of which tps features are available 6.973
Then a Tails persistence partition exists on USB drive "old" 0.462
And I shutdown Tails and wait for the computer to power off 4.284
After features/support/hooks.rb:339 0.345
After features/support/hooks.rb:108 0.005
Tags: @product
1:39.789
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.559
Then Tails is running from USB drive "old" 0.221
And all tps features are active 7.529
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.458
And all persistent directories from the old Tails version have safe access rights 2.027
And I take note of which tps features are available 6.916
And I shutdown Tails and wait for the computer to power off 4.061
# 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.408
After features/support/hooks.rb:339 0.631
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.771
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 9.059
And I log in to a new session 11.914
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.828
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.384
Then the running Tails is installed on USB drive "to_upgrade" 21.066
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:339 1.802
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.858
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.084
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.042
Then all tps features from the old Tails version are active 1.187
And Tails is running from USB drive "to_upgrade" 0.235
And the boot device has safe access rights 2.609
And the expected persistent files created with the old Tails version are present in the filesystem 0.926
And all persistent directories from the old Tails version have safe access rights 1.773
After features/support/hooks.rb:339 0.798
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:41.310
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.479
And no SquashFS delta is installed 0.144
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.338
When the network is plugged 0.025
And Tor is ready 12.769
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.979
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.081
Given I shutdown Tails and wait for the computer to power off 5.355
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.091
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.794
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.230
When the network is plugged 0.021
And Tor is ready 10.695
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.224
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.942
Given I shutdown Tails and wait for the computer to power off 2.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.450
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.428
And the file system changes introduced in version 6.3~testoverlayfs are present 0.307
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.027
And Tor is ready 10.660
Then the Upgrader considers the system as up-to-date 0.103
# 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.609
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.402
After features/support/hooks.rb:339 1.359
After features/support/hooks.rb:108 0.028
Tags: @product @automatic_upgrade
22.114
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.310
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
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.036
And Tor is ready 8.732
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.661
After features/support/hooks.rb:339 0.743
After features/support/hooks.rb:108 0.000