Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 97 07 Jun 2024, 06:37

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:3.890 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:2.628
Before features/support/hooks.rb:269 0.005
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 29.795
When I start Tails from USB drive "old" with network unplugged 1:27.841
Then the boot device has safe access rights 2.799
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.295
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:315 7.127
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.609
Before features/support/hooks.rb:269 0.005
Given a computer 0.171
And I start Tails from USB drive "old" with network unplugged and I login 1:21.652
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 34.886
And I take note of which tps features are available 1.363
Then a Tails persistence partition exists on USB drive "old" 0.695
And I shutdown Tails and wait for the computer to power off 8.512
After features/support/hooks.rb:315 0.149
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.638
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.003
Then Tails is running from USB drive "old" 0.371
And all tps features are active 1.952
When I write some files expected to persist 1.601
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.244
And I take note of which tps features are available 0.385
And I shutdown Tails and wait for the computer to power off 4.308
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.018
After features/support/hooks.rb:315 0.084
After features/support/hooks.rb:100 0.009
Tags: @product
2:23.010
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.771
And I log in to a new session 17.638
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.373
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.056
Then the running Tails is installed on USB drive "to_upgrade" 18.420
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:315 6.679
After features/support/hooks.rb:100 0.000
Tags: @product
2:8.440
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:59.890
Then all tps features from the old Tails version are active 1.540
And Tails is running from USB drive "to_upgrade" 0.288
And the boot device has safe access rights 2.857
And the expected persistent files created with the old Tails version are present in the filesystem 1.443
And all persistent directories from the old Tails version have safe access rights 2.235
After features/support/hooks.rb:315 0.829
After features/support/hooks.rb:100 0.009
6:8.570
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.587
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.402
When the network is plugged 0.048
And Tor is ready 18.036
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.365
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.696
Given I shutdown Tails and wait for the computer to power off 8.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.083
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.075
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.395
# 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.221
When the network is plugged 0.044
And Tor is ready 19.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.473
Given I shutdown Tails and wait for the computer to power off 4.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.619
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.485
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.339
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.036
And Tor is ready 18.752
Then the Upgrader considers the system as up-to-date 0.299
# 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 13.393
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.846
After features/support/hooks.rb:315 0.748
After features/support/hooks.rb:100 0.015
31.993
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.295
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.937
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 15.017
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.398
After features/support/hooks.rb:315 0.674
After features/support/hooks.rb:100 0.000