Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 123 01 Jul 2024, 06:46

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:45.208 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:40.768
Before features/support/hooks.rb:269 0.009
Given a computer 0.847
And I create a 7200 MiB disk named "old" 0.122
And I plug USB drive "old" 1.072
And I write an old version of the Tails USB image to disk "old" 32.736
When I start Tails from USB drive "old" with network unplugged 2:1.851
Then the boot device has safe access rights 3.134
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.322
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:326 3.510
After features/support/hooks.rb:100 0.040
Tags: @product
2:4.931
Before features/support/hooks.rb:269 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login 1:24.977
Then Tails is running from USB drive "old" 0.334
And I create a persistent partition 30.802
And I take note of which tps features are available 1.594
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 6.255
After features/support/hooks.rb:326 0.182
After features/support/hooks.rb:100 0.009
Tags: @product
2:57.396
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.027
Then Tails is running from USB drive "old" 0.401
And all tps features are active 2.852
When I write some files expected to persist 2.004
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.258
And all persistence configuration files have safe access rights 0.440
And all persistent directories from the old Tails version have safe access rights 3.089
And I take note of which tps features are available 0.777
And I shutdown Tails and wait for the computer to power off 4.452
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.885
After features/support/hooks.rb:326 0.146
After features/support/hooks.rb:100 0.008
Tags: @product
2:46.126
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 25.161
And I log in to a new session 18.998
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 2.355
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.750
Then the running Tails is installed on USB drive "to_upgrade" 22.539
And I unplug USB drive "to_upgrade" 0.355
And I unplug USB drive "__internal" 0.381
After features/support/hooks.rb:326 1.954
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.418
Before features/support/hooks.rb:269 0.006
Given a computer 0.423
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.569
Then all tps features from the old Tails version are active 2.372
And Tails is running from USB drive "to_upgrade" 0.346
And the boot device has safe access rights 3.817
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.482
After features/support/hooks.rb:326 0.701
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:59.457
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.347
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
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.395
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.051
And Tor is ready 21.600
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.141
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.055
Given I shutdown Tails and wait for the computer to power off 10.036
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.643
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.472
And the file system changes introduced in version 6.2~testoverlayfs are present 0.357
And only the 6.2~testoverlayfs SquashFS delta is installed 0.096
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.454
When the network is plugged 0.045
And Tor is ready 18.787
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.746
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.702
Given I shutdown Tails and wait for the computer to power off 7.381
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:13.716
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 3.723
And the file system changes introduced in version 6.3~testoverlayfs are present 0.502
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.346
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.309
When the network is plugged 0.145
And Tor is ready 18.237
Then the Upgrader considers the system as up-to-date 0.337
# 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.437
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.939
After features/support/hooks.rb:326 0.806
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
1:2.108
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 11.499
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.965
But a current signing key is available on our website 0.000
When the network is plugged 0.192
And Tor is ready 48.446
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.659
After features/support/hooks.rb:326 0.971
After features/support/hooks.rb:100 0.000