Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 9 04 Apr 2026, 02:10

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.291 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:6.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
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.058
When I start Tails from USB drive "old" with network unplugged 48.627
Then the boot device has safe access rights 2.751
And Tails is running from USB drive "old" 0.245
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.388
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.936
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 52.283
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 23.059
And I take note of which tps features are available 0.601
Then a Tails persistence partition exists on USB drive "old" 0.492
And I shutdown Tails and wait for the computer to power off 8.178
After features/support/hooks.rb:331 0.392
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.550
Then Tails is running from USB drive "old" 0.240
And all tps features are active 1.077
When I write some files expected to persist 1.206
# 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.450
And all persistent directories from the old Tails version have safe access rights 1.800
And I take note of which tps features are available 0.141
And I shutdown Tails and wait for the computer to power off 8.164
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.658
After features/support/hooks.rb:331 0.321
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.022
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 without a persistent partition and stopped at Tails Greeter's login screen 8.214
And I log in to a new session 11.889
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.944
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.280
Then the running Tails is installed on USB drive "to_upgrade" 15.179
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:331 2.190
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.669
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.197
Then all tps features from the old Tails version are active 0.919
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.268
And the expected persistent files created with the old Tails version are present in the filesystem 1.187
And all persistent directories from the old Tails version have safe access rights 1.818
After features/support/hooks.rb:331 0.545
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:29.344
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 8.334
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.017
And Tor is ready 20.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.341
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.292
Given I shutdown Tails and wait for the computer to power off 19.693
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.064
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.078
And the file system changes introduced in version 6.2~testoverlayfs are present 0.247
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.197
When the network is plugged 0.011
And Tor is ready 20.322
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.344
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.694
Given I shutdown Tails and wait for the computer to power off 13.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.233
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.221
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.023
And Tor is ready 20.960
Then the Upgrader considers the system as up-to-date 0.113
# 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.310
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.342
After features/support/hooks.rb:331 1.106
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
26.635
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.672
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.277
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 18.136
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.608
After features/support/hooks.rb:100 0.000