Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 96 06 Jun 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 19:36.322 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:34.564
Before features/support/hooks.rb:269 0.005
Given a computer 0.197
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.067
And I write an old version of the Tails USB image to disk "old" 26.985
When I start Tails from USB drive "old" with network unplugged 2:2.343
Then the boot device has safe access rights 2.920
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.319
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:315 8.224
After features/support/hooks.rb:100 0.010
Tags: @product
2:8.046
Before features/support/hooks.rb:269 0.008
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:21.050
Then Tails is running from USB drive "old" 0.364
And I create a persistent partition 35.770
And I take note of which tps features are available 1.552
Then a Tails persistence partition exists on USB drive "old" 0.768
And I shutdown Tails and wait for the computer to power off 8.338
After features/support/hooks.rb:315 0.132
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.541
Before features/support/hooks.rb:269 0.006
Given a computer 0.219
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:12.743
Then Tails is running from USB drive "old" 0.381
And all tps features are active 2.118
When I write some files expected to persist 2.108
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.771
And all persistence configuration files have safe access rights 0.452
And all persistent directories from the old Tails version have safe access rights 2.371
And I take note of which tps features are available 0.430
And I shutdown Tails and wait for the computer to power off 4.334
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.609
After features/support/hooks.rb:315 0.152
After features/support/hooks.rb:100 0.013
Tags: @product
2:35.889
Before features/support/hooks.rb:269 0.015
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.450
And I log in to a new session 22.161
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.433
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.270
Then the running Tails is installed on USB drive "to_upgrade" 19.657
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.246
After features/support/hooks.rb:315 2.064
After features/support/hooks.rb:100 0.000
Tags: @product
2:18.400
Before features/support/hooks.rb:269 0.007
Given a computer 0.243
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.778
Then all tps features from the old Tails version are active 1.650
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.371
And the expected persistent files created with the old Tails version are present in the filesystem 1.645
And all persistent directories from the old Tails version have safe access rights 2.396
After features/support/hooks.rb:315 0.746
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:32.318
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 18.842
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.317
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.482
When the network is plugged 0.048
And Tor is ready 19.629
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.337
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.969
Given I shutdown Tails and wait for the computer to power off 9.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.955
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 4.820
And the file system changes introduced in version 6.2~testoverlayfs are present 0.331
And only the 6.2~testoverlayfs SquashFS delta is installed 0.090
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.401
# 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.317
When the network is plugged 0.500
And Tor is ready 19.233
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.277
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.653
Given I shutdown Tails and wait for the computer to power off 7.024
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.230
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.328
And the file system changes introduced in version 6.3~testoverlayfs are present 0.630
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.338
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.263
When the network is plugged 0.041
And Tor is ready 17.954
Then the Upgrader considers the system as up-to-date 0.339
# 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 14.362
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.078
After features/support/hooks.rb:315 0.726
After features/support/hooks.rb:100 0.047
Tags: @product @automatic_upgrade
35.561
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 9.618
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.415
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.978
But a current signing key is available on our website 0.000
When the network is plugged 0.313
And Tor is ready 17.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.621
After features/support/hooks.rb:315 1.054
After features/support/hooks.rb:100 0.000