Project Number Date
test_Tails_ISO_20671-electrum-campaign-2024 3 22 Nov 2024, 03:31

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:17.340 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:0.522
Before features/support/hooks.rb:269 0.006
Given a computer 0.214
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 29.146
When I start Tails from USB drive "old" with network unplugged 1:26.278
Then the boot device has safe access rights 2.793
And Tails is running from USB drive "old" 0.326
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.121
And udev-watchdog is monitoring the correct device 0.296
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:326 3.513
After features/support/hooks.rb:100 0.015
Tags: @product
2:2.051
Before features/support/hooks.rb:269 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login 1:19.738
Then Tails is running from USB drive "old" 0.342
And I create a persistent partition 31.117
And I take note of which tps features are available 1.701
Then a Tails persistence partition exists on USB drive "old" 0.770
And I shutdown Tails and wait for the computer to power off 8.183
After features/support/hooks.rb:326 0.174
After features/support/hooks.rb:100 0.009
Tags: @product
2:38.619
Before features/support/hooks.rb:269 0.006
Given a computer 0.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:2.665
Then Tails is running from USB drive "old" 0.960
And all tps features are active 2.030
When I write some files expected to persist 1.508
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 2.256
And I take note of which tps features are available 0.398
And I shutdown Tails and wait for the computer to power off 4.268
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.814
After features/support/hooks.rb:326 0.100
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.669
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.343
And I log in to a new session 19.458
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.843
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.925
Then the running Tails is installed on USB drive "to_upgrade" 20.293
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.202
After features/support/hooks.rb:326 2.435
After features/support/hooks.rb:100 0.000
Tags: @product
2:16.315
Before features/support/hooks.rb:269 0.007
Given a computer 0.196
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.012
Then all tps features from the old Tails version are active 1.706
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.193
And the expected persistent files created with the old Tails version are present in the filesystem 1.437
And all persistent directories from the old Tails version have safe access rights 2.425
After features/support/hooks.rb:326 0.681
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:9.966
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.647
And no SquashFS delta is installed 0.289
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.850
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.254
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.084
And Tor is ready 23.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.523
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.799
Given I shutdown Tails and wait for the computer to power off 8.422
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.079
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.260
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.272
When the network is plugged 0.058
And Tor is ready 15.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.462
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.178
Given I shutdown Tails and wait for the computer to power off 4.480
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.156
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.475
And only the 6.3~testoverlayfs SquashFS delta is installed 0.064
# 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.365
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.296
When the network is plugged 0.076
And Tor is ready 17.378
Then the Upgrader considers the system as up-to-date 0.331
# 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.962
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.084
After features/support/hooks.rb:326 0.721
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
41.195
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.421
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.734
But a current signing key is available on our website 0.000
When the network is plugged 0.081
And Tor is ready 22.412
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.284
After features/support/hooks.rb:326 0.868
After features/support/hooks.rb:100 0.000