Project Number Date
test_Tails_ISO_stable 5917 29 Oct 2025, 14:21

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:37.649 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:0.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.282
And I create a 7200 MiB disk named "old" 0.070
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 26.877
When I start Tails from USB drive "old" with network unplugged 1:27.700
Then the boot device has safe access rights 2.921
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.380
And I unplug USB drive "old" 0.210
After features/support/hooks.rb:331 3.814
After features/support/hooks.rb:100 0.009
Tags: @product
2:10.862
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login 1:28.984
Then Tails is running from USB drive "old" 0.316
And I create a persistent partition 28.908
And I take note of which tps features are available 2.682
Then a Tails persistence partition exists on USB drive "old" 1.995
And I shutdown Tails and wait for the computer to power off 7.757
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.008
Tags: @product
2:10.308
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:40.044
Then Tails is running from USB drive "old" 0.311
And all tps features are active 2.309
When I write some files expected to persist 2.056
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.221
And all persistence configuration files have safe access rights 0.402
And all persistent directories from the old Tails version have safe access rights 2.470
And I take note of which tps features are available 0.607
And I shutdown Tails and wait for the computer to power off 3.430
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.242
After features/support/hooks.rb:331 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
2:37.713
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 16.175
And I log in to a new session 16.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.836
And I plug USB drive "to_upgrade" 2.590
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.007
Then the running Tails is installed on USB drive "to_upgrade" 20.900
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:331 3.793
After features/support/hooks.rb:100 0.000
Tags: @product
1:52.553
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.268
Then all tps features from the old Tails version are active 1.529
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 3.223
And the expected persistent files created with the old Tails version are present in the filesystem 1.442
And all persistent directories from the old Tails version have safe access rights 2.563
After features/support/hooks.rb:331 1.004
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:20.036
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 12.602
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.292
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.075
And Tor is ready 15.012
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.687
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.228
Given I shutdown Tails and wait for the computer to power off 10.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.772
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.264
And the file system changes introduced in version 6.2~testoverlayfs are present 0.289
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.177
# 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.278
When the network is plugged 0.072
And Tor is ready 12.411
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.884
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.775
Given I shutdown Tails and wait for the computer to power off 8.004
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.804
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.631
And the file system changes introduced in version 6.3~testoverlayfs are present 0.458
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.065
And Tor is ready 12.325
Then the Upgrader considers the system as up-to-date 10.837
# 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 5.713
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.539
After features/support/hooks.rb:331 1.192
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
26.111
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.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.259
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.074
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 11.351
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.140
After features/support/hooks.rb:331 0.818
After features/support/hooks.rb:100 0.000