Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 43 15 Apr 2024, 06:14

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 16:47.820 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:35.428
Before features/support/hooks.rb:259 0.005
Given a computer 0.201
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 18.983
When I start Tails from USB drive "old" with network unplugged 1:10.915
Then the boot device has safe access rights 3.179
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.080
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.230
After features/support/hooks.rb:305 7.148
After features/support/hooks.rb:89 0.009
Tags: @product
1:58.679
Before features/support/hooks.rb:259 0.004
Given a computer 0.251
And I start Tails from USB drive "old" with network unplugged and I login 1:16.236
Then Tails is running from USB drive "old" 0.337
And I create a persistent partition 32.662
And I take note of which tps features are available 1.586
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 6.725
After features/support/hooks.rb:305 0.179
After features/support/hooks.rb:89 0.010
Tags: @product
2:26.362
Before features/support/hooks.rb:259 0.007
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.168
Then Tails is running from USB drive "old" 0.372
And all tps features are active 2.002
When I write some files expected to persist 1.712
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.442
And all persistent directories from the old Tails version have safe access rights 2.605
And I take note of which tps features are available 0.558
And I shutdown Tails and wait for the computer to power off 4.300
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.791
After features/support/hooks.rb:305 0.106
After features/support/hooks.rb:89 0.018
Tags: @product
2:17.366
Before features/support/hooks.rb:259 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 9.826
And I log in to a new session 16.066
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.346
And I plug USB drive "to_upgrade" 2.421
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.061
Then the running Tails is installed on USB drive "to_upgrade" 12.241
And I unplug USB drive "to_upgrade" 0.226
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:305 3.575
After features/support/hooks.rb:89 0.000
Tags: @product
1:57.355
Before features/support/hooks.rb:259 0.006
Given a computer 0.201
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.406
Then all tps features from the old Tails version are active 1.722
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 2.902
And the expected persistent files created with the old Tails version are present in the filesystem 1.321
And all persistent directories from the old Tails version have safe access rights 2.496
After features/support/hooks.rb:305 0.779
After features/support/hooks.rb:89 0.009
5:59.100
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.514
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.374
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.045
And Tor is ready 17.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.896
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.491
Given I shutdown Tails and wait for the computer to power off 6.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.580
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.297
And only the 6.2~testoverlayfs SquashFS delta is installed 0.080
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.309
# 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.286
When the network is plugged 0.040
And Tor is ready 16.140
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.110
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.808
Given I shutdown Tails and wait for the computer to power off 4.282
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.705
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.559
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.304
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.056
And Tor is ready 14.601
Then the Upgrader considers the system as up-to-date 0.268
# 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.203
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.956
After features/support/hooks.rb:305 0.759
After features/support/hooks.rb:89 0.015
33.527
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.634
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.474
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.431
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 16.717
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.170
After features/support/hooks.rb:305 0.653
After features/support/hooks.rb:89 0.000