Project Number Date
test_Tails_ISO_21721-less-verbose-release-process 2 29 Aug 2026, 20:57

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:28.850 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:12.371
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.649
When I start Tails from USB drive "old" with network unplugged 54.922
Then the boot device has safe access rights 2.093
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.121
After features/support/hooks.rb:339 3.696
After features/support/hooks.rb:108 0.026
Tags: @product
1:21.568
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.102
And I start Tails from USB drive "old" with network unplugged and I login 47.307
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 23.802
And I take note of which tps features are available 6.909
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 2.734
After features/support/hooks.rb:339 0.289
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.805
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.116
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.990
Then Tails is running from USB drive "old" 0.221
And all tps features are active 7.292
When I write some files expected to persist 0.925
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.320
And all persistent directories from the old Tails version have safe access rights 2.320
And I take note of which tps features are available 6.227
And I shutdown Tails and wait for the computer to power off 3.983
# 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.269
After features/support/hooks.rb:339 0.466
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.066
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.397
And I log in to a new session 12.283
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.603
And I plug USB drive "to_upgrade" 2.295
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.464
Then the running Tails is installed on USB drive "to_upgrade" 17.719
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 1.927
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.042
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
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.572
Then all tps features from the old Tails version are active 1.029
And Tails is running from USB drive "to_upgrade" 0.179
And the boot device has safe access rights 2.536
And the expected persistent files created with the old Tails version are present in the filesystem 0.963
And all persistent directories from the old Tails version have safe access rights 1.664
After features/support/hooks.rb:339 0.666
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:40.793
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.224
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.230
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.033
And Tor is ready 14.781
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.307
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.215
Given I shutdown Tails and wait for the computer to power off 5.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.547
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.912
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.169
When the network is plugged 0.566
And Tor is ready 9.983
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.448
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.799
Given I shutdown Tails and wait for the computer to power off 2.644
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.832
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.246
And the file system changes introduced in version 6.3~testoverlayfs are present 0.395
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.088
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.025
And Tor is ready 10.270
Then the Upgrader considers the system as up-to-date 10.420
# 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.541
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 1.044
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.203
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.748
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.218
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.924
After features/support/hooks.rb:339 0.958
After features/support/hooks.rb:108 0.000