Project Number Date
test_Tails_ISO_20898-tinyrpc-drop 12 24 Apr 2025, 00:53

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:8.626 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:13.066
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.234
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.226
When I start Tails from USB drive "old" with network unplugged 1:38.060
Then the boot device has safe access rights 3.415
And Tails is running from USB drive "old" 0.350
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.320
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:330 3.793
After features/support/hooks.rb:100 0.008
Tags: @product
2:11.016
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:26.268
Then Tails is running from USB drive "old" 0.402
And I create a persistent partition 33.278
And I take note of which tps features are available 1.769
Then a Tails persistence partition exists on USB drive "old" 0.767
And I shutdown Tails and wait for the computer to power off 8.340
After features/support/hooks.rb:330 0.180
After features/support/hooks.rb:100 0.008
Tags: @product
3:11.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:32.513
Then Tails is running from USB drive "old" 0.457
And all tps features are active 2.077
When I write some files expected to persist 1.940
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.796
And I take note of which tps features are available 0.728
And I shutdown Tails and wait for the computer to power off 4.453
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.573
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.008
Tags: @product
2:35.892
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 11.103
And I log in to a new session 21.130
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.838
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.989
Then the running Tails is installed on USB drive "to_upgrade" 23.984
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:330 0.881
After features/support/hooks.rb:100 0.000
Tags: @product
2:20.777
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.758
Then all tps features from the old Tails version are active 1.793
And Tails is running from USB drive "to_upgrade" 0.341
And the boot device has safe access rights 3.664
And the expected persistent files created with the old Tails version are present in the filesystem 1.488
And all persistent directories from the old Tails version have safe access rights 2.543
After features/support/hooks.rb:330 1.233
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:55.190
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 11.173
And no SquashFS delta is installed 0.293
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.477
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.290
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.489
When the network is plugged 0.117
And Tor is ready 20.811
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.142
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.438
Given I shutdown Tails and wait for the computer to power off 11.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.015
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.600
And the file system changes introduced in version 6.2~testoverlayfs are present 0.360
And only the 6.2~testoverlayfs SquashFS delta is installed 0.094
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.371
# 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.307
When the network is plugged 0.083
And Tor is ready 18.678
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.168
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 12.559
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.773
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 2.226
And the file system changes introduced in version 6.3~testoverlayfs are present 0.522
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.065
And Tor is ready 18.994
Then the Upgrader considers the system as up-to-date 0.315
# 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.822
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.751
After features/support/hooks.rb:330 0.709
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.271
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 11.629
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.695
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.085
And Tor is ready 19.425
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.285
After features/support/hooks.rb:330 0.850
After features/support/hooks.rb:100 0.000