Project Number Date
test_Tails_ISO_devel 4318 04 Apr 2026, 11:34

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:59.960 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:14.526
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.933
When I start Tails from USB drive "old" with network unplugged 55.997
Then the boot device has safe access rights 2.790
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 1.349
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.189
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 55.750
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 23.743
And I take note of which tps features are available 0.656
Then a Tails persistence partition exists on USB drive "old" 0.567
And I shutdown Tails and wait for the computer to power off 8.137
After features/support/hooks.rb:331 0.144
After features/support/hooks.rb:100 0.007
Tags: @product
1:20.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.059
Then Tails is running from USB drive "old" 0.279
And all tps features are active 1.292
When I write some files expected to persist 1.217
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.394
And all persistent directories from the old Tails version have safe access rights 1.878
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 2.812
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.145
After features/support/hooks.rb:331 0.391
After features/support/hooks.rb:100 0.007
Tags: @product
2:22.757
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.758
And I log in to a new session 18.756
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.766
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.674
Then the running Tails is installed on USB drive "to_upgrade" 16.225
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.187
After features/support/hooks.rb:331 5.579
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.268
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.798
Then all tps features from the old Tails version are active 0.839
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.514
And the expected persistent files created with the old Tails version are present in the filesystem 1.095
And all persistent directories from the old Tails version have safe access rights 1.739
After features/support/hooks.rb:331 0.473
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:33.001
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 9.590
And no SquashFS delta is installed 0.156
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.280
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.201
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.019
And Tor is ready 25.390
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.906
Given I shutdown Tails and wait for the computer to power off 18.165
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.764
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.015
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
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.124
# 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.190
When the network is plugged 0.013
And Tor is ready 21.875
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.398
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.151
Given I shutdown Tails and wait for the computer to power off 13.214
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.835
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.077
And the file system changes introduced in version 6.3~testoverlayfs are present 0.380
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.013
And Tor is ready 21.052
Then the Upgrader considers the system as up-to-date 0.115
# 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.226
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:331 0.660
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
48.782
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.364
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 40.532
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.430
After features/support/hooks.rb:331 1.038
After features/support/hooks.rb:100 0.000