Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 110 18 Jun 2024, 06:40

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:53.718 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:56.451
Before features/support/hooks.rb:269 0.006
Given a computer 0.186
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 29.937
When I start Tails from USB drive "old" with network unplugged 1:21.429
Then the boot device has safe access rights 2.882
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:320 7.084
After features/support/hooks.rb:100 0.010
Tags: @product
2:4.225
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:20.333
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 33.167
And I take note of which tps features are available 1.245
Then a Tails persistence partition exists on USB drive "old" 0.819
And I shutdown Tails and wait for the computer to power off 8.177
After features/support/hooks.rb:320 0.152
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.837
Before features/support/hooks.rb:269 0.006
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.697
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.831
When I write some files expected to persist 1.811
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
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.454
And I take note of which tps features are available 0.420
And I shutdown Tails and wait for the computer to power off 4.468
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.067
After features/support/hooks.rb:320 0.094
After features/support/hooks.rb:100 0.010
Tags: @product
2:46.776
Before features/support/hooks.rb:269 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 29.074
And I log in to a new session 16.123
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.622
And I plug USB drive "to_upgrade" 2.379
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.821
Then the running Tails is installed on USB drive "to_upgrade" 23.357
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:320 4.405
After features/support/hooks.rb:100 0.000
Tags: @product
2:5.969
Before features/support/hooks.rb:269 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:56.987
Then all tps features from the old Tails version are active 1.540
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 2.888
And the expected persistent files created with the old Tails version are present in the filesystem 1.629
And all persistent directories from the old Tails version have safe access rights 2.363
After features/support/hooks.rb:320 0.693
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:40.953
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.011
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.509
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.044
And Tor is ready 48.610
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.574
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.842
Given I shutdown Tails and wait for the computer to power off 8.454
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.899
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.043
And the file system changes introduced in version 6.2~testoverlayfs are present 0.308
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.319
# 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.283
When the network is plugged 0.049
And Tor is ready 17.408
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.117
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.751
Given I shutdown Tails and wait for the computer to power off 4.310
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.763
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.938
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.102
# 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.369
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.042
And Tor is ready 19.161
Then the Upgrader considers the system as up-to-date 0.309
# 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.940
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.922
After features/support/hooks.rb:320 0.728
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
33.504
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.609
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.520
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.885
But a current signing key is available on our website 0.000
When the network is plugged 0.120
And Tor is ready 18.719
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.581
After features/support/hooks.rb:320 0.831
After features/support/hooks.rb:100 0.000