Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 3 17 Mar 2024, 06:10

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:4.995 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:29.160
Before features/support/hooks.rb:245 0.006
Given a computer 0.149
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 18.273
When I start Tails from USB drive "old" with network unplugged 1:6.058
Then the boot device has safe access rights 2.702
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.263
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:291 6.689
After features/support/hooks.rb:75 0.009
Tags: @product
2:4.714
Before features/support/hooks.rb:245 0.007
Given a computer 0.160
And I start Tails from USB drive "old" with network unplugged and I login 1:13.822
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 40.795
And I take note of which tps features are available 1.830
Then a Tails persistence partition exists on USB drive "old" 0.791
And I shutdown Tails and wait for the computer to power off 7.023
After features/support/hooks.rb:291 0.169
After features/support/hooks.rb:75 0.010
Tags: @product
2:20.223
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 with persistence enabled 1:54.602
Then Tails is running from USB drive "old" 0.327
And all tps features are active 1.629
When I write some files expected to persist 1.558
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.267
And I take note of which tps features are available 0.422
And I shutdown Tails and wait for the computer to power off 4.215
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.493
After features/support/hooks.rb:291 0.105
After features/support/hooks.rb:75 0.010
Tags: @product
2:26.796
Before features/support/hooks.rb:245 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 10.372
And I log in to a new session 14.867
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.370
And I plug USB drive "to_upgrade" 2.389
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.322
Then the running Tails is installed on USB drive "to_upgrade" 12.053
And I unplug USB drive "to_upgrade" 0.190
And I unplug USB drive "__internal" 0.229
After features/support/hooks.rb:291 3.559
After features/support/hooks.rb:75 0.000
Tags: @product
1:53.848
Before features/support/hooks.rb:245 0.008
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.138
Then all tps features from the old Tails version are active 1.268
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 2.577
And the expected persistent files created with the old Tails version are present in the filesystem 1.296
And all persistent directories from the old Tails version have safe access rights 2.098
After features/support/hooks.rb:291 0.600
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:16.395
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 10.427
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.332
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.387
When the network is plugged 0.028
And Tor is ready 20.180
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.939
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.252
Given I shutdown Tails and wait for the computer to power off 6.138
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.437
Then Tails is running version 6.2~testoverlayfs 0.027
And all tps features are active 1.614
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.347
# 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.356
When the network is plugged 0.093
And Tor is ready 15.714
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.332
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.662
Given I shutdown Tails and wait for the computer to power off 4.019
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.948
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.672
And the file system changes introduced in version 6.3~testoverlayfs are present 0.422
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.276
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.261
When the network is plugged 0.029
And Tor is ready 43.734
Then the Upgrader considers the system as up-to-date 0.232
# 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 12.632
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.079
After features/support/hooks.rb:291 0.666
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
33.856
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 9.591
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 1.063
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 16.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.306
After features/support/hooks.rb:291 0.690
After features/support/hooks.rb:75 0.000