Project Number Date
test_Tails_ISO_test-suite-early-boot-hooks 13 16 Dec 2024, 15:40

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:51.559 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:20.643
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 34.483
When I start Tails from USB drive "old" with network unplugged 1:39.680
Then the boot device has safe access rights 3.924
And Tails is running from USB drive "old" 0.386
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.114
And udev-watchdog is monitoring the correct device 0.354
And I unplug USB drive "old" 0.275
After features/support/hooks.rb:330 3.919
After features/support/hooks.rb:100 0.013
Tags: @product
2:22.708
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:38.919
Then Tails is running from USB drive "old" 0.370
And I create a persistent partition 32.117
And I take note of which tps features are available 1.348
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 8.819
After features/support/hooks.rb:330 0.185
After features/support/hooks.rb:100 0.011
Tags: @product
3:6.961
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.218
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:29.876
Then Tails is running from USB drive "old" 0.455
And all tps features are active 1.978
When I write some files expected to persist 1.685
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.234
And all persistence configuration files have safe access rights 0.420
And all persistent directories from the old Tails version have safe access rights 2.563
And I take note of which tps features are available 0.528
And I shutdown Tails and wait for the computer to power off 4.458
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.542
After features/support/hooks.rb:330 0.130
After features/support/hooks.rb:100 0.012
Tags: @product
2:39.722
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.202
And I log in to a new session 22.578
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.986
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.228
Then the running Tails is installed on USB drive "to_upgrade" 20.761
And I unplug USB drive "to_upgrade" 0.250
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:330 3.119
After features/support/hooks.rb:100 0.000
Tags: @product
2:12.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.980
Then all tps features from the old Tails version are active 1.704
And Tails is running from USB drive "to_upgrade" 0.317
And the boot device has safe access rights 3.391
And the expected persistent files created with the old Tails version are present in the filesystem 1.652
And all persistent directories from the old Tails version have safe access rights 2.668
After features/support/hooks.rb:330 1.389
After features/support/hooks.rb:100 0.010
6:29.859
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.796
And no SquashFS delta is installed 0.191
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.581
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.108
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.062
And Tor is ready 22.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.252
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.825
Given I shutdown Tails and wait for the computer to power off 10.735
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.021
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.244
And the file system changes introduced in version 6.2~testoverlayfs are present 0.317
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.304
# 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.291
When the network is plugged 0.069
And Tor is ready 18.302
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.775
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.552
Given I shutdown Tails and wait for the computer to power off 4.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.882
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.234
And the file system changes introduced in version 6.3~testoverlayfs are present 0.570
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.283
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.083
And Tor is ready 18.040
Then the Upgrader considers the system as up-to-date 0.321
# 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.965
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.070
After features/support/hooks.rb:330 0.831
After features/support/hooks.rb:100 0.021
38.733
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.862
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the signing key used by the Upgrader is outdated 0.985
But a current signing key is available on our website 0.000
When the network is plugged 0.355
And Tor is ready 20.062
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.029
After features/support/hooks.rb:330 0.974
After features/support/hooks.rb:100 0.000