Project Number Date
test_Tails_ISO_devel 3326 18 Mar 2024, 15:49

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:30.639 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:31.559
Before features/support/hooks.rb:245 0.005
Given a computer 0.169
And I create a 7200 MiB disk named "old" 0.037
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 20.587
When I start Tails from USB drive "old" with network unplugged 1:5.557
Then the boot device has safe access rights 3.154
And Tails is running from USB drive "old" 0.357
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:291 7.098
After features/support/hooks.rb:75 0.011
Tags: @product
2:3.134
Before features/support/hooks.rb:245 0.008
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login 1:20.648
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 32.116
And I take note of which tps features are available 2.036
Then a Tails persistence partition exists on USB drive "old" 0.747
And I shutdown Tails and wait for the computer to power off 7.062
After features/support/hooks.rb:291 0.163
After features/support/hooks.rb:75 0.012
Tags: @product
2:22.049
Before features/support/hooks.rb:245 0.006
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:57.137
Then Tails is running from USB drive "old" 0.343
And all tps features are active 1.778
When I write some files expected to persist 1.592
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.247
And all persistence configuration files have safe access rights 0.389
And all persistent directories from the old Tails version have safe access rights 2.374
And I take note of which tps features are available 0.343
And I shutdown Tails and wait for the computer to power off 3.068
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.594
After features/support/hooks.rb:291 0.166
After features/support/hooks.rb:75 0.011
Tags: @product
2:18.769
Before features/support/hooks.rb:245 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 11.362
And I log in to a new session 16.391
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.443
And I plug USB drive "to_upgrade" 2.412
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.923
Then the running Tails is installed on USB drive "to_upgrade" 11.860
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:291 6.377
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.769
Before features/support/hooks.rb:245 0.007
Given a computer 0.161
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.557
Then all tps features from the old Tails version are active 1.275
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.829
And the expected persistent files created with the old Tails version are present in the filesystem 1.306
And all persistent directories from the old Tails version have safe access rights 2.319
After features/support/hooks.rb:291 0.680
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:45.500
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.663
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.485
When the network is plugged 0.036
And Tor is ready 18.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.559
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.364
Given I shutdown Tails and wait for the computer to power off 6.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.617
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.700
And the file system changes introduced in version 6.2~testoverlayfs are present 0.282
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.298
# 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.238
When the network is plugged 0.029
And Tor is ready 13.902
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.472
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.857
Given I shutdown Tails and wait for the computer to power off 4.020
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.172
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.690
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.313
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.264
When the network is plugged 0.026
And Tor is ready 17.082
Then the Upgrader considers the system as up-to-date 0.218
# 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 13.889
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.844
After features/support/hooks.rb:291 0.782
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
32.855
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.805
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.462
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 17.118
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.108
After features/support/hooks.rb:291 0.903
After features/support/hooks.rb:75 0.000