Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 76 18 May 2024, 06:46

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:23.543 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:20.931
Before features/support/hooks.rb:259 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 41.536
When I start Tails from USB drive "old" with network unplugged 1:34.124
Then the boot device has safe access rights 2.964
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:305 3.567
After features/support/hooks.rb:89 0.009
Tags: @product
2:12.197
Before features/support/hooks.rb:259 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:23.352
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 37.115
And I take note of which tps features are available 1.825
Then a Tails persistence partition exists on USB drive "old" 0.833
And I shutdown Tails and wait for the computer to power off 8.520
After features/support/hooks.rb:305 0.172
After features/support/hooks.rb:89 0.009
Tags: @product
2:53.397
Before features/support/hooks.rb:259 0.005
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.840
Then Tails is running from USB drive "old" 0.391
And all tps features are active 2.270
When I write some files expected to persist 1.747
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.240
And all persistence configuration files have safe access rights 0.456
And all persistent directories from the old Tails version have safe access rights 2.757
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 4.110
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.923
After features/support/hooks.rb:305 0.128
After features/support/hooks.rb:89 0.009
Tags: @product
2:39.282
Before features/support/hooks.rb:259 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 14.551
And I log in to a new session 19.154
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.522
And I plug USB drive "to_upgrade" 2.413
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.585
Then the running Tails is installed on USB drive "to_upgrade" 25.615
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:305 2.623
After features/support/hooks.rb:89 0.000
Tags: @product
2:18.387
Before features/support/hooks.rb:259 0.006
Given a computer 0.228
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:6.344
Then all tps features from the old Tails version are active 1.799
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 5.162
And the expected persistent files created with the old Tails version are present in the filesystem 1.643
And all persistent directories from the old Tails version have safe access rights 2.869
After features/support/hooks.rb:305 0.720
After features/support/hooks.rb:89 0.026
Tags: @product @automatic_upgrade
7:22.476
Before features/support/hooks.rb:259 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.302
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.369
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.406
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.038
And Tor is ready 24.075
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.307
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.150
Given I shutdown Tails and wait for the computer to power off 9.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:22.240
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 3.011
And the file system changes introduced in version 6.2~testoverlayfs are present 0.391
And only the 6.2~testoverlayfs SquashFS delta is installed 0.139
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.559
# 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.367
When the network is plugged 0.050
And Tor is ready 44.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.703
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.971
Given I shutdown Tails and wait for the computer to power off 4.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:7.040
Then Tails is running version 6.3~testoverlayfs 0.025
And all tps features are active 2.133
And the file system changes introduced in version 6.3~testoverlayfs are present 0.591
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.421
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.266
When the network is plugged 0.054
And Tor is ready 20.265
Then the Upgrader considers the system as up-to-date 0.349
# 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.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.103
After features/support/hooks.rb:305 0.737
After features/support/hooks.rb:89 0.040
Tags: @product @automatic_upgrade
36.870
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 10.892
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.062
And the signing key used by the Upgrader is outdated 0.814
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 17.926
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.759
After features/support/hooks.rb:305 0.758
After features/support/hooks.rb:89 0.000