Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 72 14 May 2024, 06:53

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:36.074 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:17.152
Before features/support/hooks.rb:259 0.008
Given a computer 0.221
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 31.581
When I start Tails from USB drive "old" with network unplugged 1:39.868
Then the boot device has safe access rights 3.237
And Tails is running from USB drive "old" 0.343
And there is no persistence partition on USB drive "old" 0.083
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.364
And I unplug USB drive "old" 0.247
After features/support/hooks.rb:305 3.570
After features/support/hooks.rb:89 0.031
Tags: @product
2:12.666
Before features/support/hooks.rb:259 0.006
Given a computer 0.232
And I start Tails from USB drive "old" with network unplugged and I login 1:26.164
Then Tails is running from USB drive "old" 0.308
And I create a persistent partition 35.387
And I take note of which tps features are available 1.529
Then a Tails persistence partition exists on USB drive "old" 0.815
And I shutdown Tails and wait for the computer to power off 8.228
After features/support/hooks.rb:305 0.187
After features/support/hooks.rb:89 0.009
Tags: @product
3:1.795
Before features/support/hooks.rb:259 0.007
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:23.284
Then Tails is running from USB drive "old" 0.389
And all tps features are active 2.303
When I write some files expected to persist 2.045
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.269
And all persistence configuration files have safe access rights 0.407
And all persistent directories from the old Tails version have safe access rights 2.541
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 4.466
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.451
After features/support/hooks.rb:305 0.143
After features/support/hooks.rb:89 0.013
Tags: @product
2:31.011
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.735
And I log in to a new session 21.202
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.549
And I plug USB drive "to_upgrade" 2.530
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.526
Then the running Tails is installed on USB drive "to_upgrade" 18.007
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.250
After features/support/hooks.rb:305 3.643
After features/support/hooks.rb:89 0.000
Tags: @product
2:31.203
Before features/support/hooks.rb:259 0.009
Given a computer 0.244
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:21.193
Then all tps features from the old Tails version are active 1.977
And Tails is running from USB drive "to_upgrade" 0.315
And the boot device has safe access rights 3.142
And the expected persistent files created with the old Tails version are present in the filesystem 1.835
And all persistent directories from the old Tails version have safe access rights 2.494
After features/support/hooks.rb:305 0.770
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
6:25.446
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 13.712
And no SquashFS delta is installed 0.110
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.400
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.526
When the network is plugged 0.070
And Tor is ready 20.558
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.060
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.873
Given I shutdown Tails and wait for the computer to power off 9.097
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.790
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# 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.252
When the network is plugged 0.035
And Tor is ready 17.925
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.918
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.052
Given I shutdown Tails and wait for the computer to power off 4.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.631
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.253
And the file system changes introduced in version 6.3~testoverlayfs are present 0.483
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.314
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.295
When the network is plugged 0.047
And Tor is ready 20.356
Then the Upgrader considers the system as up-to-date 0.300
# 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.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.960
After features/support/hooks.rb:305 0.794
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
36.798
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.846
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.428
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.529
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 16.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.646
After features/support/hooks.rb:305 1.708
After features/support/hooks.rb:89 0.000