Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 99 09 Jun 2024, 06:24

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:5.045 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:53.206
Before features/support/hooks.rb:269 0.006
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.957
When I start Tails from USB drive "old" with network unplugged 1:16.370
Then the boot device has safe access rights 2.680
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.275
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:315 3.485
After features/support/hooks.rb:100 0.011
Tags: @product
2:5.943
Before features/support/hooks.rb:269 0.006
Given a computer 0.189
And I start Tails from USB drive "old" with network unplugged and I login 1:20.546
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 34.575
And I take note of which tps features are available 1.338
Then a Tails persistence partition exists on USB drive "old" 0.806
And I shutdown Tails and wait for the computer to power off 8.176
After features/support/hooks.rb:315 0.161
After features/support/hooks.rb:100 0.009
Tags: @product
2:45.507
Before features/support/hooks.rb:269 0.006
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:9.708
Then Tails is running from USB drive "old" 0.344
And all tps features are active 1.778
When I write some files expected to persist 1.493
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.207
And all persistence configuration files have safe access rights 0.355
And all persistent directories from the old Tails version have safe access rights 2.553
And I take note of which tps features are available 0.356
And I shutdown Tails and wait for the computer to power off 4.630
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.878
After features/support/hooks.rb:315 0.162
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.591
Before features/support/hooks.rb:269 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 10.389
And I log in to a new session 17.340
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.442
And I plug USB drive "to_upgrade" 2.393
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.107
Then the running Tails is installed on USB drive "to_upgrade" 15.513
And I unplug USB drive "to_upgrade" 0.193
And I unplug USB drive "__internal" 0.211
After features/support/hooks.rb:315 2.657
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.214
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.277
Then all tps features from the old Tails version are active 1.486
And Tails is running from USB drive "to_upgrade" 0.305
And the boot device has safe access rights 2.977
And the expected persistent files created with the old Tails version are present in the filesystem 1.432
And all persistent directories from the old Tails version have safe access rights 2.542
After features/support/hooks.rb:315 0.972
After features/support/hooks.rb:100 0.010
6:11.911
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.618
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.286
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.276
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.409
When the network is plugged 0.035
And Tor is ready 19.999
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.891
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.283
Given I shutdown Tails and wait for the computer to power off 8.799
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:4.081
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.217
And the file system changes introduced in version 6.2~testoverlayfs are present 0.292
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.311
# 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.266
When the network is plugged 0.039
And Tor is ready 17.922
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.317
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.085
Given I shutdown Tails and wait for the computer to power off 4.287
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.992
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.756
And the file system changes introduced in version 6.3~testoverlayfs are present 0.537
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.336
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.289
When the network is plugged 0.045
And Tor is ready 17.877
Then the Upgrader considers the system as up-to-date 0.359
# 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.068
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.874
After features/support/hooks.rb:315 0.691
After features/support/hooks.rb:100 0.020
33.669
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.821
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.329
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.951
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 17.457
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.015
After features/support/hooks.rb:315 1.590
After features/support/hooks.rb:100 0.000