Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 12 07 Apr 2026, 02:35

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:34.925 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:58.223
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.912
When I start Tails from USB drive "old" with network unplugged 1:39.943
Then the boot device has safe access rights 2.632
And Tails is running from USB drive "old" 0.225
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.155
After features/support/hooks.rb:331 3.740
After features/support/hooks.rb:100 0.019
Tags: @product
1:27.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 54.495
Then Tails is running from USB drive "old" 0.242
And I create a persistent partition 24.073
And I take note of which tps features are available 0.659
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 7.835
After features/support/hooks.rb:331 0.518
After features/support/hooks.rb:100 0.008
Tags: @product
1:26.138
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.102
Then Tails is running from USB drive "old" 0.211
And all tps features are active 1.222
When I write some files expected to persist 1.236
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 1.858
And I take note of which tps features are available 0.169
And I shutdown Tails and wait for the computer to power off 8.207
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.367
After features/support/hooks.rb:331 0.232
After features/support/hooks.rb:100 0.007
Tags: @product
2:28.042
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.777
And I log in to a new session 23.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.719
And I plug USB drive "to_upgrade" 2.240
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.569
Then the running Tails is installed on USB drive "to_upgrade" 17.259
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 3.897
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.095
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.325
Then all tps features from the old Tails version are active 1.060
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.377
And the expected persistent files created with the old Tails version are present in the filesystem 1.069
And all persistent directories from the old Tails version have safe access rights 1.920
After features/support/hooks.rb:331 0.720
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:36.716
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.287
And no SquashFS delta is installed 0.312
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.400
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.503
When the network is plugged 0.014
And Tor is ready 21.893
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.433
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.151
Given I shutdown Tails and wait for the computer to power off 24.887
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:13.497
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 0.997
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.205
When the network is plugged 0.016
And Tor is ready 20.150
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.743
Given I shutdown Tails and wait for the computer to power off 17.132
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.765
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.192
When the network is plugged 0.018
And Tor is ready 20.695
Then the Upgrader considers the system as up-to-date 0.122
# 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.192
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.345
After features/support/hooks.rb:331 0.834
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
26.822
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.473
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.031
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.470
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.396
After features/support/hooks.rb:331 0.935
After features/support/hooks.rb:100 0.000