Project Number Date
test_Tails_ISO_improved-new-identity-scenario 17 16 May 2025, 13: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 18:29.434 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:0.543
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 30.776
When I start Tails from USB drive "old" with network unplugged 1:24.604
Then the boot device has safe access rights 2.917
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.082
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.293
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:330 3.531
After features/support/hooks.rb:100 0.051
Tags: @product
2:2.529
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login 1:22.430
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 30.365
And I take note of which tps features are available 2.186
Then a Tails persistence partition exists on USB drive "old" 0.753
And I shutdown Tails and wait for the computer to power off 6.237
After features/support/hooks.rb:330 0.167
After features/support/hooks.rb:100 0.009
Tags: @product
2:51.359
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.160
Then Tails is running from USB drive "old" 1.626
And all tps features are active 2.042
When I write some files expected to persist 2.834
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 3.102
And I take note of which tps features are available 0.415
And I shutdown Tails and wait for the computer to power off 6.327
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.987
After features/support/hooks.rb:330 0.099
After features/support/hooks.rb:100 0.009
Tags: @product
2:29.080
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.548
And I log in to a new session 18.692
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.659
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.831
Then the running Tails is installed on USB drive "to_upgrade" 22.533
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 2.129
After features/support/hooks.rb:100 0.000
Tags: @product
2:9.434
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.186
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.570
Then all tps features from the old Tails version are active 1.432
And Tails is running from USB drive "to_upgrade" 0.404
And the boot device has safe access rights 3.014
And the expected persistent files created with the old Tails version are present in the filesystem 1.348
And all persistent directories from the old Tails version have safe access rights 2.477
After features/support/hooks.rb:330 1.136
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:18.456
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.124
And no SquashFS delta is installed 0.238
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.377
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.421
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.455
When the network is plugged 0.080
And Tor is ready 20.965
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.719
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.208
Given I shutdown Tails and wait for the computer to power off 8.759
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.631
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.897
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.358
When the network is plugged 0.086
And Tor is ready 18.007
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.540
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.553
Given I shutdown Tails and wait for the computer to power off 4.305
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.141
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.855
And the file system changes introduced in version 6.3~testoverlayfs are present 0.582
And only the 6.3~testoverlayfs SquashFS delta is installed 0.078
# 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.391
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.255
When the network is plugged 0.070
And Tor is ready 17.314
Then the Upgrader considers the system as up-to-date 0.319
# 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 15.455
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.450
After features/support/hooks.rb:330 0.734
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.435
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.628
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.061
And Tor is ready 21.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.995
After features/support/hooks.rb:330 0.663
After features/support/hooks.rb:100 0.000