Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 74 16 May 2024, 06:55

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 19:31.777 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.030
Before features/support/hooks.rb:259 0.005
Given a computer 0.459
And I create a 7200 MiB disk named "old" 0.170
And I plug USB drive "old" 1.190
And I write an old version of the Tails USB image to disk "old" 32.029
When I start Tails from USB drive "old" with network unplugged 1:29.977
Then the boot device has safe access rights 3.126
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:305 7.039
After features/support/hooks.rb:89 0.009
Tags: @product
2:8.063
Before features/support/hooks.rb:259 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login 1:23.139
Then Tails is running from USB drive "old" 0.377
And I create a persistent partition 33.294
And I take note of which tps features are available 1.913
Then a Tails persistence partition exists on USB drive "old" 0.879
And I shutdown Tails and wait for the computer to power off 8.264
After features/support/hooks.rb:305 0.196
After features/support/hooks.rb:89 0.010
Tags: @product
2:56.554
Before features/support/hooks.rb:259 0.006
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.708
Then Tails is running from USB drive "old" 0.475
And all tps features are active 2.218
When I write some files expected to persist 1.994
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.431
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.516
And I take note of which tps features are available 0.531
And I shutdown Tails and wait for the computer to power off 4.462
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.552
After features/support/hooks.rb:305 0.114
After features/support/hooks.rb:89 0.010
Tags: @product
2:30.548
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.586
And I log in to a new session 19.110
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.842
And I plug USB drive "to_upgrade" 2.469
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.409
Then the running Tails is installed on USB drive "to_upgrade" 18.719
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:305 2.528
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.274
Before features/support/hooks.rb:259 0.008
Given a computer 0.237
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.632
Then all tps features from the old Tails version are active 1.937
And Tails is running from USB drive "to_upgrade" 0.362
And the boot device has safe access rights 3.062
And the expected persistent files created with the old Tails version are present in the filesystem 1.408
And all persistent directories from the old Tails version have safe access rights 2.631
After features/support/hooks.rb:305 0.623
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:33.207
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.613
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.315
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.052
And Tor is ready 23.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.621
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.514
Given I shutdown Tails and wait for the computer to power off 8.478
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.035
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.324
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
And only the 6.2~testoverlayfs SquashFS delta is installed 0.119
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.366
# 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.281
When the network is plugged 0.057
And Tor is ready 19.438
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.582
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.455
Given I shutdown Tails and wait for the computer to power off 4.450
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.626
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.527
And only the 6.3~testoverlayfs SquashFS delta is installed 0.115
# 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.418
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.048
And Tor is ready 20.214
Then the Upgrader considers the system as up-to-date 0.335
# 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.105
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.030
After features/support/hooks.rb:305 0.791
After features/support/hooks.rb:89 0.077
Tags: @product @automatic_upgrade
58.097
Before features/support/hooks.rb:259 0.014
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.956
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.641
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 44.372
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.657
After features/support/hooks.rb:305 0.701
After features/support/hooks.rb:89 0.000