Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 42 14 Apr 2024, 06:30

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:0.609 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:48.617
Before features/support/hooks.rb:259 0.004
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 28.496
When I start Tails from USB drive "old" with network unplugged 1:15.114
Then the boot device has safe access rights 2.793
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.088
And udev-watchdog is monitoring the correct device 0.268
And I unplug USB drive "old" 0.234
After features/support/hooks.rb:305 4.510
After features/support/hooks.rb:89 0.009
Tags: @product
2:0.618
Before features/support/hooks.rb:259 0.005
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:15.422
Then Tails is running from USB drive "old" 0.276
And I create a persistent partition 34.259
And I take note of which tps features are available 1.278
Then a Tails persistence partition exists on USB drive "old" 0.816
And I shutdown Tails and wait for the computer to power off 8.392
After features/support/hooks.rb:305 0.171
After features/support/hooks.rb:89 0.009
Tags: @product
2:28.728
Before features/support/hooks.rb:259 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.670
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.831
When I write some files expected to persist 1.513
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.710
And I take note of which tps features are available 0.467
And I shutdown Tails and wait for the computer to power off 4.429
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.010
After features/support/hooks.rb:305 0.136
After features/support/hooks.rb:89 0.017
Tags: @product
2:18.534
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.223
And I log in to a new session 15.786
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.253
And I plug USB drive "to_upgrade" 2.396
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.144
Then the running Tails is installed on USB drive "to_upgrade" 13.315
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:305 3.563
After features/support/hooks.rb:89 0.000
Tags: @product
2:0.255
Before features/support/hooks.rb:259 0.006
Given a computer 0.180
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.216
Then all tps features from the old Tails version are active 1.633
And Tails is running from USB drive "to_upgrade" 0.377
And the boot device has safe access rights 2.778
And the expected persistent files created with the old Tails version are present in the filesystem 1.418
And all persistent directories from the old Tails version have safe access rights 2.649
After features/support/hooks.rb:305 0.753
After features/support/hooks.rb:89 0.009
5:51.716
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 11.060
And no SquashFS delta is installed 0.129
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.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.412
When the network is plugged 0.033
And Tor is ready 18.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.666
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.705
Given I shutdown Tails and wait for the computer to power off 6.544
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.558
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.082
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.277
When the network is plugged 0.057
And Tor is ready 17.382
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.174
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.456
Given I shutdown Tails and wait for the computer to power off 4.463
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.284
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.513
And only the 6.3~testoverlayfs SquashFS delta is installed 0.085
# 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.404
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.304
When the network is plugged 0.037
And Tor is ready 18.914
Then the Upgrader considers the system as up-to-date 0.254
# 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.301
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.831
After features/support/hooks.rb:305 0.731
After features/support/hooks.rb:89 0.017
32.139
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 9.687
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.333
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.125
And the signing key used by the Upgrader is outdated 0.995
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 14.233
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.727
After features/support/hooks.rb:305 1.027
After features/support/hooks.rb:89 0.000