Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 39 12 Apr 2024, 06:27

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 16:48.246 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:38.254
Before features/support/hooks.rb:259 0.008
Given a computer 0.180
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 18.788
When I start Tails from USB drive "old" with network unplugged 1:14.081
Then the boot device has safe access rights 3.116
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.098
And udev-watchdog is monitoring the correct device 0.311
And I unplug USB drive "old" 0.205
After features/support/hooks.rb:305 3.760
After features/support/hooks.rb:89 0.010
Tags: @product
2:2.596
Before features/support/hooks.rb:259 0.007
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:19.517
Then Tails is running from USB drive "old" 0.324
And I create a persistent partition 32.173
And I take note of which tps features are available 1.310
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 8.308
After features/support/hooks.rb:305 0.180
After features/support/hooks.rb:89 0.011
Tags: @product
2:22.024
Before features/support/hooks.rb:259 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.643
Then Tails is running from USB drive "old" 0.348
And all tps features are active 1.906
When I write some files expected to persist 1.616
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.339
And all persistent directories from the old Tails version have safe access rights 2.728
And I take note of which tps features are available 0.394
And I shutdown Tails and wait for the computer to power off 4.141
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.494
After features/support/hooks.rb:305 0.104
After features/support/hooks.rb:89 0.012
Tags: @product
2:18.828
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.232
And I log in to a new session 15.777
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.401
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.757
Then the running Tails is installed on USB drive "to_upgrade" 12.811
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:305 6.756
After features/support/hooks.rb:89 0.000
Tags: @product
1:59.548
Before features/support/hooks.rb:259 0.008
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.371
Then all tps features from the old Tails version are active 1.583
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 3.259
And the expected persistent files created with the old Tails version are present in the filesystem 1.521
And all persistent directories from the old Tails version have safe access rights 2.288
After features/support/hooks.rb:305 0.868
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
5:52.289
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.880
And no SquashFS delta is installed 0.349
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.041
And Tor is ready 23.149
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.028
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.861
Given I shutdown Tails and wait for the computer to power off 6.507
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.800
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.372
And the file system changes introduced in version 6.2~testoverlayfs are present 0.336
And only the 6.2~testoverlayfs SquashFS delta is installed 0.138
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.299
When the network is plugged 0.047
And Tor is ready 14.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.307
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.363
Given I shutdown Tails and wait for the computer to power off 4.368
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.298
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.971
And the file system changes introduced in version 6.3~testoverlayfs are present 0.456
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.288
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.225
When the network is plugged 0.053
And Tor is ready 22.758
Then the Upgrader considers the system as up-to-date 0.265
# 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.112
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.914
After features/support/hooks.rb:305 1.040
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
34.705
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 10.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.402
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the signing key used by the Upgrader is outdated 0.402
But a current signing key is available on our website 0.000
When the network is plugged 0.195
And Tor is ready 18.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.007
After features/support/hooks.rb:305 0.754
After features/support/hooks.rb:89 0.000