Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 67 07 May 2024, 06: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 19:35.719 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
2:18.867
Before features/support/hooks.rb:259 0.007
Given a computer 0.229
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 31.718
When I start Tails from USB drive "old" with network unplugged 1:41.369
Then the boot device has safe access rights 3.290
And Tails is running from USB drive "old" 0.417
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.351
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:305 7.351
After features/support/hooks.rb:89 0.012
Tags: @product
2:11.769
Before features/support/hooks.rb:259 0.008
Given a computer 0.405
And I start Tails from USB drive "old" with network unplugged and I login 1:24.907
Then Tails is running from USB drive "old" 0.438
And I create a persistent partition 35.216
And I take note of which tps features are available 1.416
Then a Tails persistence partition exists on USB drive "old" 0.876
And I shutdown Tails and wait for the computer to power off 8.507
After features/support/hooks.rb:305 0.181
After features/support/hooks.rb:89 0.010
Tags: @product
2:52.234
Before features/support/hooks.rb:259 0.006
Given a computer 0.348
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.563
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.976
When I write some files expected to persist 1.901
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.246
And all persistence configuration files have safe access rights 0.546
And all persistent directories from the old Tails version have safe access rights 2.498
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 4.230
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.052
After features/support/hooks.rb:305 0.158
After features/support/hooks.rb:89 0.009
Tags: @product
2:28.342
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 12.429
And I log in to a new session 19.527
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.742
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.878
Then the running Tails is installed on USB drive "to_upgrade" 15.883
And I unplug USB drive "to_upgrade" 0.225
And I unplug USB drive "__internal" 0.191
After features/support/hooks.rb:305 2.598
After features/support/hooks.rb:89 0.000
Tags: @product
2:10.346
Before features/support/hooks.rb:259 0.008
Given a computer 0.177
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.114
Then all tps features from the old Tails version are active 1.670
And Tails is running from USB drive "to_upgrade" 0.312
And the boot device has safe access rights 3.003
And the expected persistent files created with the old Tails version are present in the filesystem 1.604
And all persistent directories from the old Tails version have safe access rights 2.464
After features/support/hooks.rb:305 0.795
After features/support/hooks.rb:89 0.011
Tags: @product @automatic_upgrade
6:58.066
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 12.939
And no SquashFS delta is installed 0.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
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.528
When the network is plugged 0.047
And Tor is ready 20.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.729
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.884
Given I shutdown Tails and wait for the computer to power off 13.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.080
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.566
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.260
When the network is plugged 0.052
And Tor is ready 17.882
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.218
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.801
Given I shutdown Tails and wait for the computer to power off 4.497
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.353
Then Tails is running version 6.3~testoverlayfs 0.019
And all tps features are active 2.371
And the file system changes introduced in version 6.3~testoverlayfs are present 0.470
And only the 6.3~testoverlayfs SquashFS delta is installed 0.081
# 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.293
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.049
And Tor is ready 45.251
Then the Upgrader considers the system as up-to-date 0.322
# 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.957
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.927
After features/support/hooks.rb:305 0.754
After features/support/hooks.rb:89 0.018
Tags: @product @automatic_upgrade
36.093
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.495
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.460
But a current signing key is available on our website 0.000
When the network is plugged 0.066
And Tor is ready 17.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.769
After features/support/hooks.rb:305 0.911
After features/support/hooks.rb:89 0.000