Project Number Date
test_Tails_ISO_devel 4188 24 Jan 2026, 11:48

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 12:7.826 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:13.521
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.996
When I start Tails from USB drive "old" with network unplugged 55.220
Then the boot device has safe access rights 2.504
And Tails is running from USB drive "old" 0.275
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:331 3.571
After features/support/hooks.rb:100 0.030
Tags: @product
1:30.327
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 55.187
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 25.007
And I take note of which tps features are available 0.758
Then a Tails persistence partition exists on USB drive "old" 0.648
And I shutdown Tails and wait for the computer to power off 8.447
After features/support/hooks.rb:331 0.563
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.920
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.133
When I write some files expected to persist 1.278
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 1.731
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 8.342
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.247
After features/support/hooks.rb:331 0.175
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.574
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.429
And I log in to a new session 10.330
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.557
Then the running Tails is installed on USB drive "to_upgrade" 15.960
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.147
After features/support/hooks.rb:331 2.475
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.364
Then all tps features from the old Tails version are active 0.972
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.488
And the expected persistent files created with the old Tails version are present in the filesystem 1.171
And all persistent directories from the old Tails version have safe access rights 2.269
After features/support/hooks.rb:331 0.864
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:12.368
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.405
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.330
When the network is plugged 0.018
And Tor is ready 12.707
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.639
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.907
Given I shutdown Tails and wait for the computer to power off 9.478
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.374
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.165
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.163
# 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.324
When the network is plugged 0.021
And Tor is ready 41.178
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.421
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.171
Given I shutdown Tails and wait for the computer to power off 8.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.921
Then Tails is running version 6.3~testoverlayfs 0.023
And all tps features are active 1.084
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.014
And Tor is ready 10.631
Then the Upgrader considers the system as up-to-date 10.624
# 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 4.243
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:331 1.039
After features/support/hooks.rb:100 0.056
Tags: @product @automatic_upgrade
20.833
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.707
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the signing key used by the Upgrader is outdated 0.117
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.430
After features/support/hooks.rb:331 0.962
After features/support/hooks.rb:100 0.000