Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 75 17 May 2024, 06:48

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:5.489 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.397
Before features/support/hooks.rb:259 0.006
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 29.472
When I start Tails from USB drive "old" with network unplugged 1:33.205
Then the boot device has safe access rights 3.333
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.084
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.347
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:305 7.580
After features/support/hooks.rb:89 0.011
Tags: @product
2:20.641
Before features/support/hooks.rb:259 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login 1:33.055
Then Tails is running from USB drive "old" 0.423
And I create a persistent partition 36.336
And I take note of which tps features are available 1.378
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 8.467
After features/support/hooks.rb:305 0.161
After features/support/hooks.rb:89 0.010
Tags: @product
2:53.081
Before features/support/hooks.rb:259 0.007
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.897
Then Tails is running from USB drive "old" 0.402
And all tps features are active 6.505
When I write some files expected to persist 1.885
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.457
And all persistent directories from the old Tails version have safe access rights 2.665
And I take note of which tps features are available 0.585
And I shutdown Tails and wait for the computer to power off 4.427
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.805
After features/support/hooks.rb:305 0.133
After features/support/hooks.rb:89 0.010
Tags: @product
2:30.107
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.798
And I log in to a new session 21.829
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.742
And I plug USB drive "to_upgrade" 2.473
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.051
Then the running Tails is installed on USB drive "to_upgrade" 16.762
And I unplug USB drive "to_upgrade" 0.265
And I unplug USB drive "__internal" 0.184
After features/support/hooks.rb:305 7.999
After features/support/hooks.rb:89 0.000
Tags: @product
2:12.095
Before features/support/hooks.rb:259 0.006
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.112
Then all tps features from the old Tails version are active 2.251
And Tails is running from USB drive "to_upgrade" 0.367
And the boot device has safe access rights 3.894
And the expected persistent files created with the old Tails version are present in the filesystem 1.574
And all persistent directories from the old Tails version have safe access rights 2.669
After features/support/hooks.rb:305 0.596
After features/support/hooks.rb:89 0.015
Tags: @product @automatic_upgrade
7:8.771
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 16.409
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.299
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.036
And Tor is ready 50.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.643
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.946
Given I shutdown Tails and wait for the computer to power off 11.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.332
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.164
And the file system changes introduced in version 6.2~testoverlayfs are present 0.325
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.346
# 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.295
When the network is plugged 0.064
And Tor is ready 21.791
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.911
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.446
Given I shutdown Tails and wait for the computer to power off 4.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.628
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.134
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
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.409
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.258
When the network is plugged 0.043
And Tor is ready 17.075
Then the Upgrader considers the system as up-to-date 10.812
# 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.681
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.919
After features/support/hooks.rb:305 0.716
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
52.393
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 24.874
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.282
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.084
And the signing key used by the Upgrader is outdated 0.501
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 20.174
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.442
After features/support/hooks.rb:305 0.773
After features/support/hooks.rb:89 0.000