Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 52 23 Apr 2024, 06:48

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:9.166 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:1.669
Before features/support/hooks.rb:259 0.007
Given a computer 0.212
And I create a 7200 MiB disk named "old" 0.059
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.718
When I start Tails from USB drive "old" with network unplugged 1:26.711
Then the boot device has safe access rights 2.926
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.197
After features/support/hooks.rb:305 3.537
After features/support/hooks.rb:89 0.037
Tags: @product
1:56.097
Before features/support/hooks.rb:259 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login 1:14.423
Then Tails is running from USB drive "old" 0.357
And I create a persistent partition 32.884
And I take note of which tps features are available 1.265
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 6.214
After features/support/hooks.rb:305 0.137
After features/support/hooks.rb:89 0.011
Tags: @product
2:40.424
Before features/support/hooks.rb:259 0.006
Given a computer 0.207
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:4.563
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.793
When I write some files expected to persist 1.550
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.233
And all persistence configuration files have safe access rights 0.350
And all persistent directories from the old Tails version have safe access rights 2.332
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 4.345
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.217
After features/support/hooks.rb:305 0.113
After features/support/hooks.rb:89 0.010
Tags: @product
2:24.745
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 11.695
And I log in to a new session 17.182
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.431
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.723
Then the running Tails is installed on USB drive "to_upgrade" 17.825
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.217
After features/support/hooks.rb:305 1.943
After features/support/hooks.rb:89 0.000
Tags: @product
2:13.389
Before features/support/hooks.rb:259 0.009
Given a computer 0.242
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:3.794
Then all tps features from the old Tails version are active 1.741
And Tails is running from USB drive "to_upgrade" 0.372
And the boot device has safe access rights 3.721
And the expected persistent files created with the old Tails version are present in the filesystem 1.327
And all persistent directories from the old Tails version have safe access rights 2.187
After features/support/hooks.rb:305 0.750
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
6:13.831
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.322
And no SquashFS delta is installed 0.084
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.476
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.094
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.640
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.430
When the network is plugged 0.050
And Tor is ready 21.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.234
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.584
Given I shutdown Tails and wait for the computer to power off 8.822
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.482
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.073
And the file system changes introduced in version 6.2~testoverlayfs are present 0.323
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.312
# 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.242
When the network is plugged 0.032
And Tor is ready 19.625
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.407
Given I shutdown Tails and wait for the computer to power off 4.279
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.840
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.001
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.350
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.051
And Tor is ready 16.269
Then the Upgrader considers the system as up-to-date 0.344
# 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.909
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.940
After features/support/hooks.rb:305 0.707
After features/support/hooks.rb:89 0.033
Tags: @product @automatic_upgrade
39.009
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.206
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.515
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.665
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 19.989
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.508
After features/support/hooks.rb:305 0.774
After features/support/hooks.rb:89 0.000