Project Number Date
test_Tails_ISO_stable 5934 06 Nov 2025, 08:29

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 19:52.679 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:21.332
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.173
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 32.945
When I start Tails from USB drive "old" with network unplugged 1:43.029
Then the boot device has safe access rights 3.170
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.115
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:331 3.805
After features/support/hooks.rb:100 0.014
Tags: @product
3:0.312
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 3.744
And I start Tails from USB drive "old" with network unplugged and I login 1:40.567
Then Tails is running from USB drive "old" 0.720
And I create a persistent partition 54.374
And I take note of which tps features are available 3.031
Then a Tails persistence partition exists on USB drive "old" 0.737
And I shutdown Tails and wait for the computer to power off 17.137
After features/support/hooks.rb:331 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
3:31.938
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 with persistence enabled 2:31.536
Then Tails is running from USB drive "old" 0.720
And all tps features are active 3.068
When I write some files expected to persist 1.414
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.334
And all persistent directories from the old Tails version have safe access rights 4.251
And I take note of which tps features are available 21.966
And I shutdown Tails and wait for the computer to power off 9.260
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.975
After features/support/hooks.rb:331 0.388
After features/support/hooks.rb:100 0.010
Tags: @product
3:12.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 30.864
And I log in to a new session 17.606
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.287
And I plug USB drive "to_upgrade" 2.799
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:58.455
Then the running Tails is installed on USB drive "to_upgrade" 21.227
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 4.280
After features/support/hooks.rb:100 0.000
Tags: @product
1:58.012
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.613
Then all tps features from the old Tails version are active 2.545
And Tails is running from USB drive "to_upgrade" 0.340
And the boot device has safe access rights 3.607
And the expected persistent files created with the old Tails version are present in the filesystem 1.410
And all persistent directories from the old Tails version have safe access rights 2.327
After features/support/hooks.rb:331 0.925
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:21.947
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.776
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.326
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.495
When the network is plugged 0.059
And Tor is ready 16.306
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.713
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.956
Given I shutdown Tails and wait for the computer to power off 11.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.659
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 7.180
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.222
When the network is plugged 0.054
And Tor is ready 12.423
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.840
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.856
Given I shutdown Tails and wait for the computer to power off 7.283
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.850
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.450
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.181
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.056
And Tor is ready 12.911
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 5.200
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.437
After features/support/hooks.rb:331 0.846
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
26.495
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.934
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
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.052
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 11.399
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.701
After features/support/hooks.rb:331 1.008
After features/support/hooks.rb:100 0.000