Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 1 15 Mar 2024, 06:37

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:58.205 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:29.908
Before features/support/hooks.rb:245 0.006
Given a computer 0.150
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 18.624
When I start Tails from USB drive "old" with network unplugged 1:6.543
Then the boot device has safe access rights 2.612
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.170
After features/support/hooks.rb:291 3.532
After features/support/hooks.rb:75 0.009
Tags: @product
2:0.442
Before features/support/hooks.rb:245 0.006
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:11.498
Then Tails is running from USB drive "old" 0.279
And I create a persistent partition 38.871
And I take note of which tps features are available 1.813
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 7.030
After features/support/hooks.rb:291 0.126
After features/support/hooks.rb:75 0.010
Tags: @product
2:29.276
Before features/support/hooks.rb:245 0.006
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:3.783
Then Tails is running from USB drive "old" 0.349
And all tps features are active 1.647
When I write some files expected to persist 1.526
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.219
And I take note of which tps features are available 0.342
And I shutdown Tails and wait for the computer to power off 4.128
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.567
After features/support/hooks.rb:291 0.109
After features/support/hooks.rb:75 0.010
Tags: @product
2:27.324
Before features/support/hooks.rb:245 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 9.947
And I log in to a new session 15.463
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.239
And I plug USB drive "to_upgrade" 2.375
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:44.968
Then the running Tails is installed on USB drive "to_upgrade" 12.959
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.173
After features/support/hooks.rb:291 3.556
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.781
Before features/support/hooks.rb:245 0.007
Given a computer 0.158
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.868
Then all tps features from the old Tails version are active 1.277
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 2.763
And the expected persistent files created with the old Tails version are present in the filesystem 1.237
And all persistent directories from the old Tails version have safe access rights 2.196
After features/support/hooks.rb:291 0.573
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:1.503
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.075
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.036
And Tor is ready 20.001
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.398
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.295
Given I shutdown Tails and wait for the computer to power off 6.021
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.682
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 1.667
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.303
# 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.298
When the network is plugged 0.035
And Tor is ready 47.552
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.606
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.141
Given I shutdown Tails and wait for the computer to power off 4.017
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.689
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.609
And the file system changes introduced in version 6.3~testoverlayfs are present 0.418
And only the 6.3~testoverlayfs SquashFS delta is installed 0.088
# 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.276
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.259
When the network is plugged 0.027
And Tor is ready 14.431
Then the Upgrader considers the system as up-to-date 0.230
# 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.015
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.915
After features/support/hooks.rb:291 0.759
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
33.967
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.435
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.736
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 18.499
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.974
After features/support/hooks.rb:291 0.639
After features/support/hooks.rb:75 0.000