Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 79 21 May 2024, 06:39

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:40.981 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.900
Before features/support/hooks.rb:259 0.005
Given a computer 0.188
And I create a 7200 MiB disk named "old" 0.054
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.367
When I start Tails from USB drive "old" with network unplugged 1:29.186
Then the boot device has safe access rights 3.047
And Tails is running from USB drive "old" 0.349
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.099
And udev-watchdog is monitoring the correct device 0.306
And I unplug USB drive "old" 0.183
After features/support/hooks.rb:305 7.288
After features/support/hooks.rb:89 0.008
Tags: @product
2:17.326
Before features/support/hooks.rb:259 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login 1:33.070
Then Tails is running from USB drive "old" 0.350
And I create a persistent partition 34.592
And I take note of which tps features are available 1.884
Then a Tails persistence partition exists on USB drive "old" 0.807
And I shutdown Tails and wait for the computer to power off 6.406
After features/support/hooks.rb:305 0.151
After features/support/hooks.rb:89 0.009
Tags: @product
2:56.151
Before features/support/hooks.rb:259 0.006
Given a computer 0.299
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:18.420
Then Tails is running from USB drive "old" 0.421
And all tps features are active 1.968
When I write some files expected to persist 1.704
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.391
And all persistent directories from the old Tails version have safe access rights 2.709
And I take note of which tps features are available 0.455
And I shutdown Tails and wait for the computer to power off 4.461
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.097
After features/support/hooks.rb:305 0.131
After features/support/hooks.rb:89 0.010
Tags: @product
2:29.265
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.719
And I log in to a new session 17.985
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.583
And I plug USB drive "to_upgrade" 3.445
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.632
Then the running Tails is installed on USB drive "to_upgrade" 16.507
And I unplug USB drive "to_upgrade" 0.211
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:305 2.570
After features/support/hooks.rb:89 0.000
Tags: @product
2:17.872
Before features/support/hooks.rb:259 0.005
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.423
Then all tps features from the old Tails version are active 1.661
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 3.158
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.540
After features/support/hooks.rb:305 0.817
After features/support/hooks.rb:89 0.014
Tags: @product @automatic_upgrade
6:56.239
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 12.867
And no SquashFS delta is installed 0.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.052
And Tor is ready 19.780
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.649
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.740
Given I shutdown Tails and wait for the computer to power off 13.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:10.565
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.634
And the file system changes introduced in version 6.2~testoverlayfs are present 0.358
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.355
# 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.316
When the network is plugged 0.042
And Tor is ready 22.416
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.362
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.903
Given I shutdown Tails and wait for the computer to power off 4.520
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.428
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.996
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
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.386
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.047
And Tor is ready 18.044
Then the Upgrader considers the system as up-to-date 10.879
# 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 16.259
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.949
After features/support/hooks.rb:305 0.812
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
38.226
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 11.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.393
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.595
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 19.405
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.600
After features/support/hooks.rb:305 1.102
After features/support/hooks.rb:89 0.000