Project Number Date
test_Tails_ISO_stable 4543 30 Nov 2023, 19: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 17:58.528 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:29.136
Before features/support/hooks.rb:245 0.004
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.092
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 18.290
When I start Tails from USB drive "old" with network unplugged 1:5.375
Then the boot device has safe access rights 3.125
And Tails is running from USB drive "old" 0.355
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.286
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:291 3.709
After features/support/hooks.rb:75 0.008
Tags: @product
1:59.221
Before features/support/hooks.rb:245 0.005
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login 1:5.763
Then Tails is running from USB drive "old" 0.425
And I create a persistent partition 43.594
And I take note of which tps features are available 1.340
Then a Tails persistence partition exists on USB drive "old" 0.835
And I shutdown Tails and wait for the computer to power off 7.077
After features/support/hooks.rb:291 0.135
After features/support/hooks.rb:75 0.009
Tags: @product
2:28.028
Before features/support/hooks.rb:245 0.006
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:59.703
Then Tails is running from USB drive "old" 0.421
And all tps features are active 2.071
When I write some files expected to persist 1.738
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.287
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.889
And I take note of which tps features are available 0.526
And I shutdown Tails and wait for the computer to power off 3.165
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.330
After features/support/hooks.rb:291 0.114
After features/support/hooks.rb:75 0.009
Tags: @product
2:31.243
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.440
And I log in to a new session 16.934
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.366
And I plug USB drive "to_upgrade" 2.479
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.081
Then the running Tails is installed on USB drive "to_upgrade" 12.574
And I unplug USB drive "to_upgrade" 0.194
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:291 3.503
After features/support/hooks.rb:75 0.000
Tags: @product
1:59.405
Before features/support/hooks.rb:245 0.005
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.562
Then all tps features from the old Tails version are active 2.398
And Tails is running from USB drive "to_upgrade" 0.343
And the boot device has safe access rights 3.762
And the expected persistent files created with the old Tails version are present in the filesystem 1.680
And all persistent directories from the old Tails version have safe access rights 3.455
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:37.654
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.980
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.397
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.103
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.480
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.627
When the network is plugged 0.319
And Tor is ready 18.372
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.903
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.093
Given I shutdown Tails and wait for the computer to power off 7.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.722
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.356
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.428
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.380
When the network is plugged 0.054
And Tor is ready 44.358
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.567
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.854
Given I shutdown Tails and wait for the computer to power off 4.082
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.317
Then Tails is running version 2.3~testoverlayfsng 0.120
And all tps features are active 2.098
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.689
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.113
# 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.331
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.465
When the network is plugged 0.037
And Tor is ready 16.726
Then the Upgrader considers the system as up-to-date 0.299
# 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 31.218
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.216
After features/support/hooks.rb:291 0.754
After features/support/hooks.rb:75 0.020
Tags: @product @automatic_upgrade
53.838
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.543
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.322
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.054
And the signing key used by the Upgrader is outdated 0.586
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 41.693
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.586
After features/support/hooks.rb:291 1.010
After features/support/hooks.rb:75 0.000