Project Number Date
test_Tails_ISO_stable 4539 28 Nov 2023, 12:48

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 17:10.383 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:33.458
Before features/support/hooks.rb:245 0.005
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 19.921
When I start Tails from USB drive "old" with network unplugged 1:8.174
Then the boot device has safe access rights 3.203
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.186
After features/support/hooks.rb:291 3.504
After features/support/hooks.rb:75 0.019
Tags: @product
2:2.509
Before features/support/hooks.rb:245 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 1:10.004
Then Tails is running from USB drive "old" 0.389
And I create a persistent partition 42.593
And I take note of which tps features are available 1.400
Then a Tails persistence partition exists on USB drive "old" 0.821
And I shutdown Tails and wait for the computer to power off 7.085
After features/support/hooks.rb:291 0.110
After features/support/hooks.rb:75 0.015
Tags: @product
2:18.647
Before features/support/hooks.rb:245 0.007
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:50.806
Then Tails is running from USB drive "old" 0.356
And all tps features are active 2.189
When I write some files expected to persist 1.824
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.298
And all persistence configuration files have safe access rights 0.721
And all persistent directories from the old Tails version have safe access rights 2.919
And I take note of which tps features are available 0.424
And I shutdown Tails and wait for the computer to power off 3.056
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.854
After features/support/hooks.rb:291 0.148
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.149
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 10.265
And I log in to a new session 15.512
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.463
And I plug USB drive "to_upgrade" 2.631
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.590
Then the running Tails is installed on USB drive "to_upgrade" 13.255
And I unplug USB drive "to_upgrade" 0.202
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:291 6.809
After features/support/hooks.rb:75 0.000
Tags: @product
2:12.125
Before features/support/hooks.rb:245 0.007
Given a computer 0.203
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.150
Then all tps features from the old Tails version are active 1.861
And Tails is running from USB drive "to_upgrade" 0.364
And the boot device has safe access rights 4.155
And the expected persistent files created with the old Tails version are present in the filesystem 1.821
And all persistent directories from the old Tails version have safe access rights 2.568
After features/support/hooks.rb:291 0.876
After features/support/hooks.rb:75 0.014
Tags: @product @automatic_upgrade
6:0.625
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.799
And no SquashFS delta is installed 0.160
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.372
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.061
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.375
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.606
When the network is plugged 0.049
And Tor is ready 16.576
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.990
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.706
Given I shutdown Tails and wait for the computer to power off 11.472
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.618
Then Tails is running version 2.2~testoverlayfsng 0.139
And all tps features are active 2.144
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.382
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.068
# 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_2.0~testoverlayfsng_to_2.3~testoverlayfsng.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 2.1~testoverlayfsng was initially installed 0.325
When the network is plugged 0.050
And Tor is ready 16.829
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.920
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.101
Given I shutdown Tails and wait for the computer to power off 4.280
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.249
Then Tails is running version 2.3~testoverlayfsng 0.104
And all tps features are active 2.137
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.554
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.089
# 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.258
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.293
When the network is plugged 0.046
And Tor is ready 16.052
Then the Upgrader considers the system as up-to-date 0.271
# 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 28.005
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.253
After features/support/hooks.rb:291 0.904
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
30.866
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.089
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.326
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.072
And the signing key used by the Upgrader is outdated 1.475
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 15.978
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.884
After features/support/hooks.rb:291 0.739
After features/support/hooks.rb:75 0.000