Project Number Date
test_Tails_ISO_improved-new-identity-scenario 16 15 May 2025, 15:05

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 20:23.761 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
2:8.554
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.065
And I plug USB drive "old" 1.077
And I write an old version of the Tails USB image to disk "old" 33.138
When I start Tails from USB drive "old" with network unplugged 1:28.913
Then the boot device has safe access rights 3.957
And Tails is running from USB drive "old" 0.453
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.117
And udev-watchdog is monitoring the correct device 0.329
And I unplug USB drive "old" 0.225
After features/support/hooks.rb:330 3.648
After features/support/hooks.rb:100 0.016
Tags: @product
2:19.552
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.014
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login 1:31.823
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 34.920
And I take note of which tps features are available 2.352
Then a Tails persistence partition exists on USB drive "old" 0.846
And I shutdown Tails and wait for the computer to power off 9.070
After features/support/hooks.rb:330 0.162
After features/support/hooks.rb:100 0.008
Tags: @product
3:5.250
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.107
Then Tails is running from USB drive "old" 1.230
And all tps features are active 2.040
When I write some files expected to persist 1.944
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.252
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 2.561
And I take note of which tps features are available 0.483
And I shutdown Tails and wait for the computer to power off 6.861
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.075
After features/support/hooks.rb:330 0.147
After features/support/hooks.rb:100 0.007
Tags: @product
2:45.810
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 without a persistent partition and stopped at Tails Greeter's login screen 15.578
And I log in to a new session 20.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.863
And I plug USB drive "to_upgrade" 2.410
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.484
Then the running Tails is installed on USB drive "to_upgrade" 27.772
And I unplug USB drive "to_upgrade" 0.261
And I unplug USB drive "__internal" 0.297
After features/support/hooks.rb:330 2.058
After features/support/hooks.rb:100 0.000
Tags: @product
2:24.706
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.297
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:14.017
Then all tps features from the old Tails version are active 1.920
And Tails is running from USB drive "to_upgrade" 0.407
And the boot device has safe access rights 3.421
And the expected persistent files created with the old Tails version are present in the filesystem 1.728
And all persistent directories from the old Tails version have safe access rights 2.914
After features/support/hooks.rb:330 1.586
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
7:1.199
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 16.070
And no SquashFS delta is installed 0.219
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.421
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.088
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.478
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.067
And Tor is ready 23.312
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.989
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.397
Given I shutdown Tails and wait for the computer to power off 10.857
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:14.584
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.690
And the file system changes introduced in version 6.2~testoverlayfs are present 0.425
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.372
# 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.345
When the network is plugged 0.070
And Tor is ready 19.918
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.443
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.171
Given I shutdown Tails and wait for the computer to power off 4.873
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:0.060
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.394
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.134
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.435
When the network is plugged 0.088
And Tor is ready 22.199
Then the Upgrader considers the system as up-to-date 0.350
# 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 17.107
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.144
After features/support/hooks.rb:330 0.871
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
38.688
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.895
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.521
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.106
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.086
And Tor is ready 19.497
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.473
After features/support/hooks.rb:330 1.124
After features/support/hooks.rb:100 0.000