Project Number Date
test_Tails_ISO_21472-circumvention-settings-2 10 05 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:4.457 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.548
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.254
When I start Tails from USB drive "old" with network unplugged 49.110
Then the boot device has safe access rights 2.481
And Tails is running from USB drive "old" 0.216
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.796
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.561
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login 51.599
Then Tails is running from USB drive "old" 0.234
And I create a persistent partition 23.643
And I take note of which tps features are available 0.598
Then a Tails persistence partition exists on USB drive "old" 0.510
And I shutdown Tails and wait for the computer to power off 7.917
After features/support/hooks.rb:331 0.288
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.452
Then Tails is running from USB drive "old" 0.298
And all tps features are active 0.991
When I write some files expected to persist 1.259
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 1.957
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 7.867
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.854
After features/support/hooks.rb:331 0.334
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.503
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.197
And I log in to a new session 11.625
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.756
And I plug USB drive "to_upgrade" 2.199
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.636
Then the running Tails is installed on USB drive "to_upgrade" 14.778
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 2.165
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.643
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 58.801
Then all tps features from the old Tails version are active 1.122
And Tails is running from USB drive "to_upgrade" 0.279
And the boot device has safe access rights 2.535
And the expected persistent files created with the old Tails version are present in the filesystem 1.074
And all persistent directories from the old Tails version have safe access rights 1.771
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:28.444
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.967
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.195
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.014
And Tor is ready 18.968
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.554
Given I shutdown Tails and wait for the computer to power off 19.716
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.318
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.204
When the network is plugged 0.016
And Tor is ready 21.742
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.756
Given I shutdown Tails and wait for the computer to power off 16.905
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.741
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.318
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.040
And Tor is ready 20.467
Then the Upgrader considers the system as up-to-date 0.117
# 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.583
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.459
After features/support/hooks.rb:331 0.990
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.273
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.449
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
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.051
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 16.058
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
After features/support/hooks.rb:331 1.018
After features/support/hooks.rb:100 0.000