Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 8 19 Mar 2024, 17: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 18:14.616 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:37.227
Before features/support/hooks.rb:245 0.005
Given a computer 0.156
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 22.056
When I start Tails from USB drive "old" with network unplugged 1:9.950
Then the boot device has safe access rights 2.952
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.083
And udev-watchdog is monitoring the correct device 0.338
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:291 6.587
After features/support/hooks.rb:75 0.009
Tags: @product
1:57.391
Before features/support/hooks.rb:245 0.006
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:17.588
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 30.819
And I take note of which tps features are available 1.682
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 6.022
After features/support/hooks.rb:291 0.211
After features/support/hooks.rb:75 0.010
Tags: @product
2:33.519
Before features/support/hooks.rb:245 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.490
Then Tails is running from USB drive "old" 0.373
And all tps features are active 1.894
When I write some files expected to persist 1.720
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.192
And all persistence configuration files have safe access rights 0.418
And all persistent directories from the old Tails version have safe access rights 2.880
And I take note of which tps features are available 0.464
And I shutdown Tails and wait for the computer to power off 4.019
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.883
After features/support/hooks.rb:291 0.182
After features/support/hooks.rb:75 0.008
Tags: @product
2:50.413
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 35.144
And I log in to a new session 16.707
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.540
And I plug USB drive "to_upgrade" 2.441
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.021
Then the running Tails is installed on USB drive "to_upgrade" 18.108
And I unplug USB drive "to_upgrade" 0.220
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:291 3.647
After features/support/hooks.rb:75 0.000
Tags: @product
2:6.418
Before features/support/hooks.rb:245 0.006
Given a computer 0.290
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.686
Then all tps features from the old Tails version are active 3.205
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.028
And the expected persistent files created with the old Tails version are present in the filesystem 2.444
And all persistent directories from the old Tails version have safe access rights 2.420
After features/support/hooks.rb:291 1.327
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:39.032
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 50.427
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.301
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.074
And Tor is ready 17.272
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.008
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.425
Given I shutdown Tails and wait for the computer to power off 7.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.286
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.877
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
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.284
# 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.259
When the network is plugged 0.035
And Tor is ready 17.535
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.575
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.652
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.218
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.689
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.306
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.243
When the network is plugged 0.035
And Tor is ready 19.414
Then the Upgrader considers the system as up-to-date 0.213
# 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.854
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.091
After features/support/hooks.rb:291 0.764
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
30.614
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.680
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
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 0.592
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 14.986
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.930
After features/support/hooks.rb:291 1.133
After features/support/hooks.rb:75 0.000