Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 41 13 Apr 2024, 06:44

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:54.406 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:39.557
Before features/support/hooks.rb:259 0.005
Given a computer 0.165
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 21.685
When I start Tails from USB drive "old" with network unplugged 1:12.868
Then the boot device has safe access rights 2.826
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.282
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:305 6.687
After features/support/hooks.rb:89 0.008
Tags: @product
2:3.938
Before features/support/hooks.rb:259 0.005
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:21.688
Then Tails is running from USB drive "old" 0.329
And I create a persistent partition 33.572
And I take note of which tps features are available 1.231
Then a Tails persistence partition exists on USB drive "old" 0.735
And I shutdown Tails and wait for the computer to power off 6.204
After features/support/hooks.rb:305 0.154
After features/support/hooks.rb:89 0.007
Tags: @product
2:29.697
Before features/support/hooks.rb:259 0.004
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:1.454
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.224
When I write some files expected to persist 1.592
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.373
And all persistent directories from the old Tails version have safe access rights 2.619
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.431
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.794
After features/support/hooks.rb:305 0.122
After features/support/hooks.rb:89 0.009
Tags: @product
2:19.958
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 9.718
And I log in to a new session 20.156
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.331
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.557
Then the running Tails is installed on USB drive "to_upgrade" 13.450
And I unplug USB drive "to_upgrade" 0.199
And I unplug USB drive "__internal" 0.166
After features/support/hooks.rb:305 6.704
After features/support/hooks.rb:89 0.000
Tags: @product
1:59.665
Before features/support/hooks.rb:259 0.004
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.141
Then all tps features from the old Tails version are active 1.601
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 2.798
And the expected persistent files created with the old Tails version are present in the filesystem 1.361
And all persistent directories from the old Tails version have safe access rights 2.264
After features/support/hooks.rb:305 0.680
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
5:48.121
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.571
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
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.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.386
When the network is plugged 0.031
And Tor is ready 16.235
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.680
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.562
Given I shutdown Tails and wait for the computer to power off 6.558
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.389
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 1.972
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.242
When the network is plugged 0.039
And Tor is ready 15.399
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.348
Given I shutdown Tails and wait for the computer to power off 4.285
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.120
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.976
And the file system changes introduced in version 6.3~testoverlayfs are present 0.462
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.033
And Tor is ready 17.751
Then the Upgrader considers the system as up-to-date 0.258
# 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.685
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.823
After features/support/hooks.rb:305 0.682
After features/support/hooks.rb:89 0.019
Tags: @product @automatic_upgrade
33.467
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.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.477
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 18.381
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.120
After features/support/hooks.rb:305 0.618
After features/support/hooks.rb:89 0.000