Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 36 10 Apr 2024, 06:27

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 16:39.859 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
1:43.085
Before features/support/hooks.rb:259 0.004
Given a computer 0.174
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 19.048
When I start Tails from USB drive "old" with network unplugged 1:19.120
Then the boot device has safe access rights 2.691
And Tails is running from USB drive "old" 0.354
And there is no persistence partition on USB drive "old" 0.062
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:305 6.611
After features/support/hooks.rb:89 0.009
Tags: @product
1:58.178
Before features/support/hooks.rb:259 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:13.684
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 33.365
And I take note of which tps features are available 1.373
Then a Tails persistence partition exists on USB drive "old" 0.743
And I shutdown Tails and wait for the computer to power off 8.512
After features/support/hooks.rb:305 0.200
After features/support/hooks.rb:89 0.022
Tags: @product
2:21.535
Before features/support/hooks.rb:259 0.005
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.325
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.876
When I write some files expected to persist 1.541
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.374
And all persistent directories from the old Tails version have safe access rights 2.271
And I take note of which tps features are available 0.584
And I shutdown Tails and wait for the computer to power off 4.321
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.500
After features/support/hooks.rb:305 0.298
After features/support/hooks.rb:89 0.009
Tags: @product
2:18.119
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 9.656
And I log in to a new session 15.781
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.341
And I plug USB drive "to_upgrade" 3.990
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.371
Then the running Tails is installed on USB drive "to_upgrade" 12.589
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:305 3.650
After features/support/hooks.rb:89 0.000
Tags: @product
1:59.365
Before features/support/hooks.rb:259 0.005
Given a computer 0.229
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:50.191
Then all tps features from the old Tails version are active 1.629
And Tails is running from USB drive "to_upgrade" 0.348
And the boot device has safe access rights 3.232
And the expected persistent files created with the old Tails version are present in the filesystem 1.459
And all persistent directories from the old Tails version have safe access rights 2.275
After features/support/hooks.rb:305 0.607
After features/support/hooks.rb:89 0.010
Tags: @product @automatic_upgrade
5:45.828
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.975
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.349
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.135
And Tor is ready 18.796
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.286
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.541
Given I shutdown Tails and wait for the computer to power off 6.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.098
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.036
And the file system changes introduced in version 6.2~testoverlayfs are present 0.259
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.277
# 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.248
When the network is plugged 0.064
And Tor is ready 16.575
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.313
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.803
Given I shutdown Tails and wait for the computer to power off 4.284
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.888
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.181
And the file system changes introduced in version 6.3~testoverlayfs are present 0.476
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.294
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.048
And Tor is ready 15.416
Then the Upgrader considers the system as up-to-date 0.219
# 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 12.654
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.809
After features/support/hooks.rb:305 0.715
After features/support/hooks.rb:89 0.030
Tags: @product @automatic_upgrade
33.745
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.351
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
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.560
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 16.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.083
After features/support/hooks.rb:305 0.602
After features/support/hooks.rb:89 0.000