Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 81 23 May 2024, 07:32

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:14.537 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:5.999
Before features/support/hooks.rb:259 0.006
Given a computer 0.426
And I create a 7200 MiB disk named "old" 0.134
And I plug USB drive "old" 1.200
And I write an old version of the Tails USB image to disk "old" 31.988
When I start Tails from USB drive "old" with network unplugged 1:27.984
Then the boot device has safe access rights 3.092
And Tails is running from USB drive "old" 0.361
And there is no persistence partition on USB drive "old" 0.078
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.385
And I unplug USB drive "old" 0.246
After features/support/hooks.rb:305 3.566
After features/support/hooks.rb:89 0.011
Tags: @product
2:12.271
Before features/support/hooks.rb:259 0.006
Given a computer 0.208
And I start Tails from USB drive "old" with network unplugged and I login 1:23.472
Then Tails is running from USB drive "old" 0.339
And I create a persistent partition 36.587
And I take note of which tps features are available 1.744
Then a Tails persistence partition exists on USB drive "old" 0.878
And I shutdown Tails and wait for the computer to power off 9.040
After features/support/hooks.rb:305 0.210
After features/support/hooks.rb:89 0.009
Tags: @product
2:56.239
Before features/support/hooks.rb:259 0.006
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:19.314
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.053
When I write some files expected to persist 1.561
# 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.421
And all persistent directories from the old Tails version have safe access rights 2.676
And I take note of which tps features are available 0.515
And I shutdown Tails and wait for the computer to power off 4.341
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.549
After features/support/hooks.rb:305 0.125
After features/support/hooks.rb:89 0.007
Tags: @product
2:30.706
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.075
And I log in to a new session 18.705
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.401
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.956
Then the running Tails is installed on USB drive "to_upgrade" 19.722
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:305 2.541
After features/support/hooks.rb:89 0.000
Tags: @product
2:22.250
Before features/support/hooks.rb:259 0.004
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:12.040
Then all tps features from the old Tails version are active 1.734
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.886
And the expected persistent files created with the old Tails version are present in the filesystem 1.484
And all persistent directories from the old Tails version have safe access rights 2.567
After features/support/hooks.rb:305 0.761
After features/support/hooks.rb:89 0.010
7:27.018
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.462
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.368
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.516
When the network is plugged 0.036
And Tor is ready 20.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.245
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.560
Given I shutdown Tails and wait for the computer to power off 8.715
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.418
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.259
And the file system changes introduced in version 6.2~testoverlayfs are present 0.273
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.348
# 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.283
When the network is plugged 0.038
And Tor is ready 18.824
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.647
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.629
Given I shutdown Tails and wait for the computer to power off 1:2.385
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.399
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.211
And the file system changes introduced in version 6.3~testoverlayfs are present 0.519
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.361
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.424
When the network is plugged 0.059
And Tor is ready 19.518
Then the Upgrader considers the system as up-to-date 0.362
# 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.766
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.832
After features/support/hooks.rb:305 0.789
After features/support/hooks.rb:89 0.022
40.051
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.143
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.360
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.948
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 21.252
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.237
After features/support/hooks.rb:305 0.844
After features/support/hooks.rb:89 0.000