Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 109 17 Jun 2024, 07:01

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 20:6.203 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:34.942
Before features/support/hooks.rb:269 0.007
Given a computer 0.260
And I create a 7200 MiB disk named "old" 0.056
And I plug USB drive "old" 1.068
And I write an old version of the Tails USB image to disk "old" 58.202
When I start Tails from USB drive "old" with network unplugged 1:30.621
Then the boot device has safe access rights 3.523
And Tails is running from USB drive "old" 0.400
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.149
And udev-watchdog is monitoring the correct device 0.359
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:320 3.597
After features/support/hooks.rb:100 0.010
Tags: @product
2:15.240
Before features/support/hooks.rb:269 0.006
Given a computer 0.302
And I start Tails from USB drive "old" with network unplugged and I login 1:23.845
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 39.382
And I take note of which tps features are available 2.034
Then a Tails persistence partition exists on USB drive "old" 0.961
And I shutdown Tails and wait for the computer to power off 8.403
After features/support/hooks.rb:320 0.135
After features/support/hooks.rb:100 0.011
Tags: @product
2:58.436
Before features/support/hooks.rb:269 0.006
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:20.415
Then Tails is running from USB drive "old" 0.433
And all tps features are active 2.019
When I write some files expected to persist 1.656
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.274
And all persistence configuration files have safe access rights 0.619
And all persistent directories from the old Tails version have safe access rights 2.831
And I take note of which tps features are available 0.462
And I shutdown Tails and wait for the computer to power off 4.444
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.054
After features/support/hooks.rb:320 0.201
After features/support/hooks.rb:100 0.014
Tags: @product
2:38.399
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.567
And I log in to a new session 21.701
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.322
And I plug USB drive "to_upgrade" 2.551
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.158
Then the running Tails is installed on USB drive "to_upgrade" 17.629
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.257
After features/support/hooks.rb:320 3.899
After features/support/hooks.rb:100 0.000
Tags: @product
2:21.888
Before features/support/hooks.rb:269 0.011
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:11.857
Then all tps features from the old Tails version are active 1.777
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.198
And the expected persistent files created with the old Tails version are present in the filesystem 1.497
And all persistent directories from the old Tails version have safe access rights 2.972
After features/support/hooks.rb:320 0.689
After features/support/hooks.rb:100 0.066
Tags: @product @automatic_upgrade
6:40.472
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 11.585
And no SquashFS delta is installed 0.169
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.341
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.035
And Tor is ready 20.589
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.279
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.779
Given I shutdown Tails and wait for the computer to power off 6.783
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:9.798
Then Tails is running version 6.2~testoverlayfs 0.074
And all tps features are active 2.522
And the file system changes introduced in version 6.2~testoverlayfs are present 0.314
And only the 6.2~testoverlayfs SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.356
# 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.262
When the network is plugged 0.038
And Tor is ready 18.866
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.916
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.463
Given I shutdown Tails and wait for the computer to power off 4.605
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.129
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 1.890
And the file system changes introduced in version 6.3~testoverlayfs are present 0.480
And only the 6.3~testoverlayfs SquashFS delta is installed 0.080
# 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.340
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.257
When the network is plugged 0.041
And Tor is ready 20.160
Then the Upgrader considers the system as up-to-date 0.314
# 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.031
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.041
After features/support/hooks.rb:320 0.846
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
36.823
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 10.954
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.357
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the signing key used by the Upgrader is outdated 1.346
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 16.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.227
After features/support/hooks.rb:320 1.086
After features/support/hooks.rb:100 0.000