Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 106 14 Jun 2024, 15:16

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:46.631 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:5.260
Before features/support/hooks.rb:269 0.007
Given a computer 0.247
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.870
When I start Tails from USB drive "old" with network unplugged 1:29.120
Then the boot device has safe access rights 2.879
And Tails is running from USB drive "old" 0.341
And there is no persistence partition on USB drive "old" 0.090
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.200
After features/support/hooks.rb:320 3.537
After features/support/hooks.rb:100 0.027
Tags: @product
2:9.497
Before features/support/hooks.rb:269 0.006
Given a computer 0.242
And I start Tails from USB drive "old" with network unplugged and I login 1:25.494
Then Tails is running from USB drive "old" 0.392
And I create a persistent partition 34.213
And I take note of which tps features are available 2.009
Then a Tails persistence partition exists on USB drive "old" 0.937
And I shutdown Tails and wait for the computer to power off 6.206
After features/support/hooks.rb:320 0.201
After features/support/hooks.rb:100 0.010
Tags: @product
2:58.539
Before features/support/hooks.rb:269 0.007
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.857
Then Tails is running from USB drive "old" 0.480
And all tps features are active 2.338
When I write some files expected to persist 1.792
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.609
And all persistent directories from the old Tails version have safe access rights 2.882
And I take note of which tps features are available 0.554
And I shutdown Tails and wait for the computer to power off 4.499
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.054
After features/support/hooks.rb:320 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.594
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.040
And I log in to a new session 19.905
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.562
And I plug USB drive "to_upgrade" 2.452
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.090
Then the running Tails is installed on USB drive "to_upgrade" 19.117
And I unplug USB drive "to_upgrade" 0.224
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:320 3.451
After features/support/hooks.rb:100 0.000
Tags: @product
2:14.958
Before features/support/hooks.rb:269 0.007
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.266
Then all tps features from the old Tails version are active 1.804
And Tails is running from USB drive "to_upgrade" 0.350
And the boot device has safe access rights 3.398
And the expected persistent files created with the old Tails version are present in the filesystem 1.386
And all persistent directories from the old Tails version have safe access rights 2.520
After features/support/hooks.rb:320 0.747
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
6:57.099
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 12.477
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.330
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.556
When the network is plugged 0.079
And Tor is ready 21.087
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.891
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.266
Given I shutdown Tails and wait for the computer to power off 9.043
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.752
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.419
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.375
# 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.303
When the network is plugged 0.034
And Tor is ready 20.103
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.632
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.531
Given I shutdown Tails and wait for the computer to power off 4.439
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:18.707
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.203
And the file system changes introduced in version 6.3~testoverlayfs are present 0.544
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.311
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.033
And Tor is ready 16.340
Then the Upgrader considers the system as up-to-date 0.310
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.006
After features/support/hooks.rb:320 0.697
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
51.682
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 23.520
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.391
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 1.709
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 18.911
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.019
After features/support/hooks.rb:320 0.708
After features/support/hooks.rb:100 0.000