Project Number Date
test_Tails_ISO_20671-electrum-campaign-2024 2 21 Nov 2024, 03:52

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:25.036 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:3.231
Before features/support/hooks.rb:269 0.005
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.007
When I start Tails from USB drive "old" with network unplugged 1:29.119
Then the boot device has safe access rights 2.912
And Tails is running from USB drive "old" 0.294
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.079
And udev-watchdog is monitoring the correct device 0.269
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:326 3.497
After features/support/hooks.rb:100 0.040
Tags: @product
2:12.928
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:29.015
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 32.947
And I take note of which tps features are available 1.395
Then a Tails persistence partition exists on USB drive "old" 0.801
And I shutdown Tails and wait for the computer to power off 8.258
After features/support/hooks.rb:326 0.128
After features/support/hooks.rb:100 0.009
Tags: @product
2:48.421
Before features/support/hooks.rb:269 0.005
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:8.347
Then Tails is running from USB drive "old" 1.584
And all tps features are active 2.045
When I write some files expected to persist 2.709
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.225
And all persistence configuration files have safe access rights 0.356
And all persistent directories from the old Tails version have safe access rights 2.416
And I take note of which tps features are available 0.480
And I shutdown Tails and wait for the computer to power off 6.258
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.811
After features/support/hooks.rb:326 0.103
After features/support/hooks.rb:100 0.009
Tags: @product
2:28.625
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.592
And I log in to a new session 19.211
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.524
And I plug USB drive "to_upgrade" 2.376
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.694
Then the running Tails is installed on USB drive "to_upgrade" 21.804
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:326 6.806
After features/support/hooks.rb:100 0.000
Tags: @product
2:10.149
Before features/support/hooks.rb:269 0.005
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.204
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 3.224
And the expected persistent files created with the old Tails version are present in the filesystem 1.301
And all persistent directories from the old Tails version have safe access rights 2.302
After features/support/hooks.rb:326 0.633
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
6:5.975
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.464
And no SquashFS delta is installed 0.282
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.447
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.434
When the network is plugged 0.059
And Tor is ready 20.458
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.293
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.805
Given I shutdown Tails and wait for the computer to power off 8.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.157
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.260
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.327
# 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.269
When the network is plugged 0.062
And Tor is ready 19.359
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.061
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.300
Given I shutdown Tails and wait for the computer to power off 4.698
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.694
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 2.002
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.313
When the network is plugged 0.067
And Tor is ready 20.672
Then the Upgrader considers the system as up-to-date 0.305
# 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.109
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.069
After features/support/hooks.rb:326 0.717
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
35.704
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.774
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.577
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.716
But a current signing key is available on our website 0.000
When the network is plugged 0.070
And Tor is ready 19.592
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 4.915
After features/support/hooks.rb:326 1.057
After features/support/hooks.rb:100 0.000