Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 61 01 May 2024, 06:36

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 18:49.302 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:0.804
Before features/support/hooks.rb:259 0.006
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 29.233
When I start Tails from USB drive "old" with network unplugged 1:26.139
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.352
And there is no persistence partition on USB drive "old" 0.071
And process "udev-watchdog" is running 0.112
And udev-watchdog is monitoring the correct device 0.399
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:305 3.568
After features/support/hooks.rb:89 0.010
Tags: @product
2:11.543
Before features/support/hooks.rb:259 0.007
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login 1:23.172
Then Tails is running from USB drive "old" 0.371
And I create a persistent partition 37.002
And I take note of which tps features are available 1.580
Then a Tails persistence partition exists on USB drive "old" 0.845
And I shutdown Tails and wait for the computer to power off 8.372
After features/support/hooks.rb:305 0.185
After features/support/hooks.rb:89 0.011
Tags: @product
2:47.998
Before features/support/hooks.rb:259 0.006
Given a computer 0.280
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.422
Then Tails is running from USB drive "old" 0.320
And all tps features are active 2.009
When I write some files expected to persist 1.649
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.395
And all persistent directories from the old Tails version have safe access rights 2.556
And I take note of which tps features are available 0.479
And I shutdown Tails and wait for the computer to power off 4.300
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.365
After features/support/hooks.rb:305 0.095
After features/support/hooks.rb:89 0.018
Tags: @product
2:29.084
Before features/support/hooks.rb:259 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 10.750
And I log in to a new session 19.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.444
And I plug USB drive "to_upgrade" 2.426
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.854
Then the running Tails is installed on USB drive "to_upgrade" 19.518
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.176
After features/support/hooks.rb:305 2.100
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.789
Before features/support/hooks.rb:259 0.006
Given a computer 0.205
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.882
Then all tps features from the old Tails version are active 1.752
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.976
And the expected persistent files created with the old Tails version are present in the filesystem 1.435
And all persistent directories from the old Tails version have safe access rights 2.253
After features/support/hooks.rb:305 0.691
After features/support/hooks.rb:89 0.016
Tags: @product @automatic_upgrade
6:28.476
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.026
And no SquashFS delta is installed 0.414
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.320
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.037
And Tor is ready 17.145
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.790
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.211
Given I shutdown Tails and wait for the computer to power off 8.517
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.041
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 2.516
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.061
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.385
# 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.265
When the network is plugged 0.047
And Tor is ready 17.126
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.697
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.110
Given I shutdown Tails and wait for the computer to power off 6.393
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.704
Then Tails is running version 6.3~testoverlayfs 0.027
And all tps features are active 2.852
And the file system changes introduced in version 6.3~testoverlayfs are present 0.479
And only the 6.3~testoverlayfs SquashFS delta is installed 0.068
# 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.331
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.342
When the network is plugged 0.039
And Tor is ready 18.308
Then the Upgrader considers the system as up-to-date 0.312
# 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.929
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.911
After features/support/hooks.rb:305 0.729
After features/support/hooks.rb:89 0.043
Tags: @product @automatic_upgrade
33.605
Before features/support/hooks.rb:259 0.023
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.547
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.427
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 15.583
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.858
After features/support/hooks.rb:305 1.054
After features/support/hooks.rb:89 0.000