Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 3 29 Mar 2026, 02:07

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:10.047 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:7.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.075
When I start Tails from USB drive "old" with network unplugged 49.933
Then the boot device has safe access rights 2.658
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.382
After features/support/hooks.rb:100 0.009
Tags: @product
1:25.418
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login 52.433
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 23.661
And I take note of which tps features are available 0.637
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 7.876
After features/support/hooks.rb:331 0.447
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.062
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.664
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.163
When I write some files expected to persist 1.171
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.472
And all persistent directories from the old Tails version have safe access rights 2.033
And I take note of which tps features are available 0.142
And I shutdown Tails and wait for the computer to power off 8.126
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.784
After features/support/hooks.rb:331 0.234
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.880
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.141
And I log in to a new session 12.425
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.750
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.189
Then the running Tails is installed on USB drive "to_upgrade" 14.860
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 1.949
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.165
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.350
Then all tps features from the old Tails version are active 0.953
And Tails is running from USB drive "to_upgrade" 0.270
And the boot device has safe access rights 2.533
And the expected persistent files created with the old Tails version are present in the filesystem 1.058
And all persistent directories from the old Tails version have safe access rights 1.938
After features/support/hooks.rb:331 0.538
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:30.700
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.134
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.241
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.349
When the network is plugged 0.016
And Tor is ready 21.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.545
Given I shutdown Tails and wait for the computer to power off 19.832
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.456
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.146
And the file system changes introduced in version 6.2~testoverlayfs are present 0.243
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.212
When the network is plugged 0.013
And Tor is ready 21.276
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.351
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.676
Given I shutdown Tails and wait for the computer to power off 16.956
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.244
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.375
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.017
And Tor is ready 21.284
Then the Upgrader considers the system as up-to-date 0.103
# 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.210
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.369
After features/support/hooks.rb:331 0.745
After features/support/hooks.rb:100 0.029
Tags: @product @automatic_upgrade
25.375
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.355
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 17.302
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.347
After features/support/hooks.rb:331 0.808
After features/support/hooks.rb:100 0.000