Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 6 19 Mar 2024, 06:28

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 17:13.961 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.346
Before features/support/hooks.rb:245 0.007
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 23.913
When I start Tails from USB drive "old" with network unplugged 1:9.220
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.312
And I unplug USB drive "old" 0.207
After features/support/hooks.rb:291 6.875
After features/support/hooks.rb:75 0.010
Tags: @product
1:59.284
Before features/support/hooks.rb:245 0.007
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:19.179
Then Tails is running from USB drive "old" 0.358
And I create a persistent partition 30.207
And I take note of which tps features are available 1.650
Then a Tails persistence partition exists on USB drive "old" 0.696
And I shutdown Tails and wait for the computer to power off 7.021
After features/support/hooks.rb:291 0.156
After features/support/hooks.rb:75 0.008
Tags: @product
2:26.110
Before features/support/hooks.rb:245 0.006
Given a computer 0.152
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.977
Then Tails is running from USB drive "old" 0.338
And all tps features are active 1.649
When I write some files expected to persist 1.577
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 2.492
And I take note of which tps features are available 0.344
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.026
After features/support/hooks.rb:291 0.103
After features/support/hooks.rb:75 0.029
Tags: @product
2:22.506
Before features/support/hooks.rb:245 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 11.121
And I log in to a new session 16.723
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.576
And I plug USB drive "to_upgrade" 2.395
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.444
Then the running Tails is installed on USB drive "to_upgrade" 13.874
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:291 6.875
After features/support/hooks.rb:75 0.000
Tags: @product
2:12.761
Before features/support/hooks.rb:245 0.009
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.883
Then all tps features from the old Tails version are active 1.398
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.029
And the expected persistent files created with the old Tails version are present in the filesystem 1.485
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:291 0.636
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:54.826
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.115
And no SquashFS delta is installed 0.085
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.059
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.499
When the network is plugged 0.044
And Tor is ready 18.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.334
Given I shutdown Tails and wait for the computer to power off 6.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.869
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 1.845
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.278
# 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.231
When the network is plugged 0.030
And Tor is ready 19.533
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.150
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.456
Given I shutdown Tails and wait for the computer to power off 4.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.357
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.702
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.303
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.229
When the network is plugged 0.040
And Tor is ready 15.695
Then the Upgrader considers the system as up-to-date 0.253
# 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.522
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.870
After features/support/hooks.rb:291 0.675
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
40.126
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.779
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.445
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 14.848
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.702
After features/support/hooks.rb:291 0.651
After features/support/hooks.rb:75 0.000