Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 13 20 Mar 2024, 07: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 17:12.504 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
1:40.823
Before features/support/hooks.rb:245 0.005
Given a computer 0.158
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 22.494
When I start Tails from USB drive "old" with network unplugged 1:12.898
Then the boot device has safe access rights 3.077
And Tails is running from USB drive "old" 0.396
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.151
And udev-watchdog is monitoring the correct device 0.313
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:291 3.513
After features/support/hooks.rb:75 0.039
Tags: @product
1:58.256
Before features/support/hooks.rb:245 0.004
Given a computer 0.158
And I start Tails from USB drive "old" with network unplugged and I login 1:15.675
Then Tails is running from USB drive "old" 0.328
And I create a persistent partition 32.789
And I take note of which tps features are available 1.490
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 7.020
After features/support/hooks.rb:291 0.204
After features/support/hooks.rb:75 0.010
Tags: @product
2:30.764
Before features/support/hooks.rb:245 0.006
Given a computer 0.154
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.700
Then Tails is running from USB drive "old" 0.303
And all tps features are active 1.711
When I write some files expected to persist 1.532
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.354
And all persistent directories from the old Tails version have safe access rights 2.506
And I take note of which tps features are available 0.325
And I shutdown Tails and wait for the computer to power off 4.147
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.776
After features/support/hooks.rb:291 0.099
After features/support/hooks.rb:75 0.009
Tags: @product
2:19.430
Before features/support/hooks.rb:245 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 10.739
And I log in to a new session 16.331
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.486
And I plug USB drive "to_upgrade" 2.383
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.026
Then the running Tails is installed on USB drive "to_upgrade" 13.034
And I unplug USB drive "to_upgrade" 0.244
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:291 3.571
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.366
Before features/support/hooks.rb:245 0.006
Given a computer 0.305
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:49.994
Then all tps features from the old Tails version are active 1.472
And Tails is running from USB drive "to_upgrade" 0.357
And the boot device has safe access rights 3.475
And the expected persistent files created with the old Tails version are present in the filesystem 1.431
And all persistent directories from the old Tails version have safe access rights 2.329
After features/support/hooks.rb:291 0.829
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:12.792
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.920
And no SquashFS delta is installed 0.124
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.313
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.437
When the network is plugged 0.026
And Tor is ready 20.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.483
Given I shutdown Tails and wait for the computer to power off 6.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.090
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 1.917
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.317
# 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.274
When the network is plugged 0.035
And Tor is ready 48.495
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.615
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.964
Given I shutdown Tails and wait for the computer to power off 4.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.667
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.652
And the file system changes introduced in version 6.3~testoverlayfs are present 0.434
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.031
And Tor is ready 18.922
Then the Upgrader considers the system as up-to-date 0.228
# 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.843
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.826
After features/support/hooks.rb:291 0.706
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
31.071
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.542
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.271
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.623
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 15.401
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.155
After features/support/hooks.rb:291 0.932
After features/support/hooks.rb:75 0.000