Project Number Date
test_Tails_ISO_stable 6194 11 Mar 2026, 07:15

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 13:1.608 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:30.832
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.250
When I start Tails from USB drive "old" with network unplugged 1:11.554
Then the boot device has safe access rights 3.185
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 3.875
After features/support/hooks.rb:100 0.008
Tags: @product
1:30.513
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 58.539
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 25.947
And I take note of which tps features are available 0.723
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 4.434
After features/support/hooks.rb:331 0.364
After features/support/hooks.rb:100 0.008
Tags: @product
1:25.544
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.981
Then Tails is running from USB drive "old" 0.244
And all tps features are active 1.140
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.039
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 4.032
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.973
After features/support/hooks.rb:331 0.286
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.179
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.414
And I log in to a new session 12.879
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.886
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.771
Then the running Tails is installed on USB drive "to_upgrade" 17.682
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:331 3.514
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.233
Then all tps features from the old Tails version are active 1.131
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.771
And the expected persistent files created with the old Tails version are present in the filesystem 1.255
And all persistent directories from the old Tails version have safe access rights 2.079
After features/support/hooks.rb:331 0.929
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:38.178
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.413
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.381
When the network is plugged 0.017
And Tor is ready 23.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.734
Given I shutdown Tails and wait for the computer to power off 16.604
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.117
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.187
And the file system changes introduced in version 6.2~testoverlayfs are present 0.309
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.157
# 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.218
When the network is plugged 0.019
And Tor is ready 20.879
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.366
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 17.589
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.435
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.185
And the file system changes introduced in version 6.3~testoverlayfs are present 0.427
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.207
When the network is plugged 0.015
And Tor is ready 20.958
Then the Upgrader considers the system as up-to-date 0.106
# 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.797
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.449
After features/support/hooks.rb:331 1.016
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.560
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.782
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 18.057
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.360
After features/support/hooks.rb:331 0.621
After features/support/hooks.rb:100 0.000