Project Number Date
test_Tails_ISO_devel 4071 13 Nov 2025, 14:31

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 16:59.313 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
2:1.981
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 30.858
When I start Tails from USB drive "old" with network unplugged 1:25.966
Then the boot device has safe access rights 3.045
And Tails is running from USB drive "old" 0.285
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:331 4.098
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 1:24.842
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 29.141
And I take note of which tps features are available 9.827
Then a Tails persistence partition exists on USB drive "old" 0.818
And I shutdown Tails and wait for the computer to power off 7.879
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.924
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.248
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.648
Then Tails is running from USB drive "old" 0.288
And all tps features are active 4.159
When I write some files expected to persist 1.555
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.209
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.215
And I take note of which tps features are available 0.425
And I shutdown Tails and wait for the computer to power off 7.666
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.139
After features/support/hooks.rb:331 0.477
After features/support/hooks.rb:100 0.009
Tags: @product
2:43.825
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.570
And I log in to a new session 18.890
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.795
And I plug USB drive "to_upgrade" 2.433
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.970
Then the running Tails is installed on USB drive "to_upgrade" 22.695
And I unplug USB drive "to_upgrade" 0.232
And I unplug USB drive "__internal" 0.236
After features/support/hooks.rb:331 3.808
After features/support/hooks.rb:100 0.000
Tags: @product
1:44.170
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.216
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.538
Then all tps features from the old Tails version are active 1.566
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 3.133
And the expected persistent files created with the old Tails version are present in the filesystem 1.304
And all persistent directories from the old Tails version have safe access rights 2.106
After features/support/hooks.rb:331 0.666
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:9.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.060
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.464
When the network is plugged 2.417
And Tor is ready 16.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.615
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.072
Given I shutdown Tails and wait for the computer to power off 11.761
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.913
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.303
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.147
# 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.242
When the network is plugged 0.050
And Tor is ready 11.891
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.842
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.750
Given I shutdown Tails and wait for the computer to power off 7.855
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:37.902
Then Tails is running version 6.3~testoverlayfs 0.028
And all tps features are active 2.338
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.206
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.061
And Tor is ready 12.644
Then the Upgrader considers the system as up-to-date 0.245
# 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 6.676
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.566
After features/support/hooks.rb:331 0.956
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
54.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
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.061
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 42.190
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.564
After features/support/hooks.rb:331 0.887
After features/support/hooks.rb:100 0.000