Project Number Date
test_Tails_ISO_devel 4141 29 Dec 2025, 11:26

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 10:49.133 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
59.376
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.049
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.214
When I start Tails from USB drive "old" with network unplugged 42.060
Then the boot device has safe access rights 2.410
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.184
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.744
After features/support/hooks.rb:100 0.016
Tags: @product
1:22.481
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 49.679
Then Tails is running from USB drive "old" 0.347
And I create a persistent partition 23.066
And I take note of which tps features are available 0.695
Then a Tails persistence partition exists on USB drive "old" 0.504
And I shutdown Tails and wait for the computer to power off 8.137
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.007
Tags: @product
1:21.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.661
Then Tails is running from USB drive "old" 0.253
And all tps features are active 1.047
When I write some files expected to persist 1.292
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 1.860
And I take note of which tps features are available 0.188
And I shutdown Tails and wait for the computer to power off 8.156
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.670
After features/support/hooks.rb:331 0.232
After features/support/hooks.rb:100 0.007
Tags: @product
2:9.267
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.905
And I log in to a new session 11.271
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.029
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.295
Then the running Tails is installed on USB drive "to_upgrade" 15.236
And I unplug USB drive "to_upgrade" 0.139
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:331 3.847
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.378
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.827
Then all tps features from the old Tails version are active 0.903
And Tails is running from USB drive "to_upgrade" 0.233
And the boot device has safe access rights 2.409
And the expected persistent files created with the old Tails version are present in the filesystem 1.098
And all persistent directories from the old Tails version have safe access rights 1.849
After features/support/hooks.rb:331 0.956
After features/support/hooks.rb:100 0.026
Tags: @product @automatic_upgrade
3:31.005
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.266
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.306
When the network is plugged 0.015
And Tor is ready 12.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.764
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.342
Given I shutdown Tails and wait for the computer to power off 9.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.129
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.072
And the file system changes introduced in version 6.2~testoverlayfs are present 0.209
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.120
# 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.180
When the network is plugged 0.014
And Tor is ready 9.847
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.900
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.633
Given I shutdown Tails and wait for the computer to power off 8.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.909
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.340
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.168
When the network is plugged 0.014
And Tor is ready 10.526
Then the Upgrader considers the system as up-to-date 10.524
# 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.127
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:331 0.837
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
20.025
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.430
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
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.038
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.935
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.320
After features/support/hooks.rb:331 0.684
After features/support/hooks.rb:100 0.000