Project Number Date
test_Tails_ISO_test-suite-early-boot-hooks 12 15 Dec 2024, 19:49

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:46.721 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:15.455
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 32.379
When I start Tails from USB drive "old" with network unplugged 1:37.367
Then the boot device has safe access rights 3.391
And Tails is running from USB drive "old" 0.347
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:330 3.748
After features/support/hooks.rb:100 0.009
Tags: @product
2:18.052
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login 1:34.478
Then Tails is running from USB drive "old" 0.387
And I create a persistent partition 31.521
And I take note of which tps features are available 1.870
Then a Tails persistence partition exists on USB drive "old" 1.033
And I shutdown Tails and wait for the computer to power off 8.589
After features/support/hooks.rb:330 0.206
After features/support/hooks.rb:100 0.007
Tags: @product
2:52.049
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:13.785
Then Tails is running from USB drive "old" 0.818
And all tps features are active 2.712
When I write some files expected to persist 1.669
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.406
And all persistent directories from the old Tails version have safe access rights 2.919
And I take note of which tps features are available 0.440
And I shutdown Tails and wait for the computer to power off 4.384
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.493
After features/support/hooks.rb:330 0.161
After features/support/hooks.rb:100 0.007
Tags: @product
2:33.827
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.376
And I log in to a new session 20.224
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.970
And I plug USB drive "to_upgrade" 2.599
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.150
Then the running Tails is installed on USB drive "to_upgrade" 21.932
And I unplug USB drive "to_upgrade" 0.335
And I unplug USB drive "__internal" 0.238
After features/support/hooks.rb:330 2.320
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.110
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.897
Then all tps features from the old Tails version are active 1.537
And Tails is running from USB drive "to_upgrade" 0.301
And the boot device has safe access rights 3.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.641
And all persistent directories from the old Tails version have safe access rights 2.322
After features/support/hooks.rb:330 1.108
After features/support/hooks.rb:100 0.036
6:54.932
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.619
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.333
And Tor is ready 17.776
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.943
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.734
Given I shutdown Tails and wait for the computer to power off 8.697
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:12.922
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.277
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.292
# 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.324
When the network is plugged 0.072
And Tor is ready 18.393
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.036
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.456
Given I shutdown Tails and wait for the computer to power off 4.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:17.012
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.998
And the file system changes introduced in version 6.3~testoverlayfs are present 0.533
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.345
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.062
And Tor is ready 21.867
Then the Upgrader considers the system as up-to-date 0.333
# 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 15.279
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.955
After features/support/hooks.rb:330 0.747
After features/support/hooks.rb:100 0.024
36.293
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.353
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 1.395
But a current signing key is available on our website 0.000
When the network is plugged 0.106
And Tor is ready 18.573
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.492
After features/support/hooks.rb:330 0.756
After features/support/hooks.rb:100 0.000