Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 47 18 Apr 2024, 22:54

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:32.450 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:41.752
Before features/support/hooks.rb:259 0.006
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 20.395
When I start Tails from USB drive "old" with network unplugged 1:16.423
Then the boot device has safe access rights 2.793
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.280
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:305 3.508
After features/support/hooks.rb:89 0.009
Tags: @product
1:56.801
Before features/support/hooks.rb:259 0.004
Given a computer 0.175
And I start Tails from USB drive "old" with network unplugged and I login 1:14.760
Then Tails is running from USB drive "old" 0.348
And I create a persistent partition 32.887
And I take note of which tps features are available 1.295
Then a Tails persistence partition exists on USB drive "old" 0.786
And I shutdown Tails and wait for the computer to power off 6.546
After features/support/hooks.rb:305 0.179
After features/support/hooks.rb:89 0.017
Tags: @product
2:29.266
Before features/support/hooks.rb:259 0.007
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.185
Then Tails is running from USB drive "old" 0.375
And all tps features are active 1.797
When I write some files expected to persist 1.660
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.194
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.717
And I take note of which tps features are available 0.392
And I shutdown Tails and wait for the computer to power off 4.592
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.808
After features/support/hooks.rb:305 0.138
After features/support/hooks.rb:89 0.010
Tags: @product
2:19.801
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.297
And I log in to a new session 16.795
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.485
And I plug USB drive "to_upgrade" 2.432
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.833
Then the running Tails is installed on USB drive "to_upgrade" 13.572
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.193
After features/support/hooks.rb:305 6.529
After features/support/hooks.rb:89 0.000
Tags: @product
2:8.719
Before features/support/hooks.rb:259 0.007
Given a computer 0.178
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:0.093
Then all tps features from the old Tails version are active 1.538
And Tails is running from USB drive "to_upgrade" 0.293
And the boot device has safe access rights 2.810
And the expected persistent files created with the old Tails version are present in the filesystem 1.527
And all persistent directories from the old Tails version have safe access rights 2.278
After features/support/hooks.rb:305 0.624
After features/support/hooks.rb:89 0.010
7:22.921
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.235
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.267
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.442
When the network is plugged 0.037
And Tor is ready 19.315
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.491
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.917
Given I shutdown Tails and wait for the computer to power off 1:4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.160
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.075
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.335
When the network is plugged 0.078
And Tor is ready 16.429
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.252
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.309
Given I shutdown Tails and wait for the computer to power off 4.729
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.435
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.890
And the file system changes introduced in version 6.3~testoverlayfs are present 0.493
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.271
When the network is plugged 0.031
And Tor is ready 17.298
Then the Upgrader considers the system as up-to-date 10.675
# 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.864
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.932
After features/support/hooks.rb:305 0.748
After features/support/hooks.rb:89 0.019
33.186
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 8.955
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.840
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 16.245
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.727
After features/support/hooks.rb:305 1.550
After features/support/hooks.rb:89 0.000