Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 13 21 Oct 2024, 07:07

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:30.867 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:9.792
Before features/support/hooks.rb:269 0.005
Given a computer 0.413
And I create a 7200 MiB disk named "old" 0.483
And I plug USB drive "old" 1.112
And I write an old version of the Tails USB image to disk "old" 31.212
When I start Tails from USB drive "old" with network unplugged 1:31.681
Then the boot device has safe access rights 3.708
And Tails is running from USB drive "old" 0.378
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.377
And I unplug USB drive "old" 0.243
After features/support/hooks.rb:326 3.645
After features/support/hooks.rb:100 0.008
Tags: @product
2:22.338
Before features/support/hooks.rb:269 0.006
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login 1:33.989
Then Tails is running from USB drive "old" 0.459
And I create a persistent partition 35.661
And I take note of which tps features are available 1.866
Then a Tails persistence partition exists on USB drive "old" 1.009
And I shutdown Tails and wait for the computer to power off 9.160
After features/support/hooks.rb:326 0.179
After features/support/hooks.rb:100 0.012
Tags: @product
3:19.653
Before features/support/hooks.rb:269 0.008
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:39.101
Then Tails is running from USB drive "old" 0.404
And all tps features are active 2.665
When I write some files expected to persist 2.029
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.306
And all persistence configuration files have safe access rights 0.487
And all persistent directories from the old Tails version have safe access rights 2.979
And I take note of which tps features are available 0.631
And I shutdown Tails and wait for the computer to power off 4.328
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 26.480
After features/support/hooks.rb:326 0.198
After features/support/hooks.rb:100 0.011
Tags: @product
2:47.813
Before features/support/hooks.rb:269 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.435
And I log in to a new session 22.857
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.151
And I plug USB drive "to_upgrade" 2.787
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.003
Then the running Tails is installed on USB drive "to_upgrade" 27.861
And I unplug USB drive "to_upgrade" 0.298
And I unplug USB drive "__internal" 0.418
After features/support/hooks.rb:326 7.103
After features/support/hooks.rb:100 0.000
Tags: @product
2:37.942
Before features/support/hooks.rb:269 0.009
Given a computer 0.276
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.962
Then all tps features from the old Tails version are active 1.949
And Tails is running from USB drive "to_upgrade" 0.421
And the boot device has safe access rights 3.335
And the expected persistent files created with the old Tails version are present in the filesystem 1.510
And all persistent directories from the old Tails version have safe access rights 2.488
After features/support/hooks.rb:326 0.785
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:35.541
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 13.069
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.295
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.483
When the network is plugged 0.088
And Tor is ready 20.454
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.541
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.379
Given I shutdown Tails and wait for the computer to power off 11.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.638
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 2.570
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.470
# 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.278
When the network is plugged 0.071
And Tor is ready 17.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.764
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.724
Given I shutdown Tails and wait for the computer to power off 4.660
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.593
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.183
And the file system changes introduced in version 6.3~testoverlayfs are present 0.734
And only the 6.3~testoverlayfs SquashFS delta is installed 0.119
# 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.447
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.316
When the network is plugged 0.069
And Tor is ready 21.360
Then the Upgrader considers the system as up-to-date 0.297
# 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.125
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.156
After features/support/hooks.rb:326 0.767
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
37.785
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.969
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.541
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 1.002
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 18.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.267
After features/support/hooks.rb:326 1.173
After features/support/hooks.rb:100 0.000