Project Number Date
test_Tails_ISO_21573-tor-0.4.9.8 1 08 May 2026, 10:04

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.922 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:2.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.353
When I start Tails from USB drive "old" with network unplugged 44.179
Then the boot device has safe access rights 2.884
And Tails is running from USB drive "old" 0.246
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.162
After features/support/hooks.rb:331 1.338
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.548
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login 56.238
Then Tails is running from USB drive "old" 0.229
And I create a persistent partition 23.873
And I take note of which tps features are available 0.829
Then a Tails persistence partition exists on USB drive "old" 0.652
And I shutdown Tails and wait for the computer to power off 5.627
After features/support/hooks.rb:331 0.338
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.238
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.970
Then Tails is running from USB drive "old" 0.281
And all tps features are active 1.175
When I write some files expected to persist 1.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.430
And all persistent directories from the old Tails version have safe access rights 2.027
And I take note of which tps features are available 0.183
And I shutdown Tails and wait for the computer to power off 8.078
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.542
After features/support/hooks.rb:331 0.613
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.150
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 7.875
And I log in to a new session 13.332
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.758
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.301
Then the running Tails is installed on USB drive "to_upgrade" 15.326
And I unplug USB drive "to_upgrade" 0.177
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 6.645
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.931
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.189
Then all tps features from the old Tails version are active 0.881
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.634
And the expected persistent files created with the old Tails version are present in the filesystem 1.053
And all persistent directories from the old Tails version have safe access rights 1.872
After features/support/hooks.rb:331 0.808
After features/support/hooks.rb:100 0.005
Tags: @product @automatic_upgrade
4:31.553
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.026
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.491
When the network is plugged 0.018
And Tor is ready 20.711
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.367
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.201
Given I shutdown Tails and wait for the computer to power off 19.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.265
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.141
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.255
When the network is plugged 0.024
And Tor is ready 22.100
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.943
Given I shutdown Tails and wait for the computer to power off 17.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.607
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.057
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.014
And Tor is ready 21.600
Then the Upgrader considers the system as up-to-date 0.126
# 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.380
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.386
After features/support/hooks.rb:331 0.851
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
24.287
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.351
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 16.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.345
After features/support/hooks.rb:331 0.932
After features/support/hooks.rb:100 0.000