Project Number Date
test_Tails_ISO_stable 4583 21 Dec 2023, 13:43

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:7.777 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:30.771
Before features/support/hooks.rb:245 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 23.028
When I start Tails from USB drive "old" with network unplugged 1:2.384
Then the boot device has safe access rights 3.120
And Tails is running from USB drive "old" 0.321
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.177
After features/support/hooks.rb:291 3.504
After features/support/hooks.rb:75 0.028
Tags: @product
1:57.943
Before features/support/hooks.rb:245 0.005
Given a computer 0.169
And I start Tails from USB drive "old" with network unplugged and I login 1:3.799
Then Tails is running from USB drive "old" 0.450
And I create a persistent partition 44.264
And I take note of which tps features are available 1.420
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 7.063
After features/support/hooks.rb:291 0.173
After features/support/hooks.rb:75 0.009
Tags: @product
2:28.486
Before features/support/hooks.rb:245 0.006
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:0.494
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.268
When I write some files expected to persist 1.840
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.320
And all persistence configuration files have safe access rights 0.604
And all persistent directories from the old Tails version have safe access rights 2.628
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 3.083
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.140
After features/support/hooks.rb:291 0.127
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.566
Before features/support/hooks.rb:245 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 10.141
And I log in to a new session 18.021
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.207
And I plug USB drive "to_upgrade" 2.440
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.553
Then the running Tails is installed on USB drive "to_upgrade" 12.793
And I unplug USB drive "to_upgrade" 0.213
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:291 6.899
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.353
Before features/support/hooks.rb:245 0.006
Given a computer 0.194
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.166
Then all tps features from the old Tails version are active 1.818
And Tails is running from USB drive "to_upgrade" 0.384
And the boot device has safe access rights 3.863
And the expected persistent files created with the old Tails version are present in the filesystem 1.884
And all persistent directories from the old Tails version have safe access rights 3.040
After features/support/hooks.rb:291 0.903
After features/support/hooks.rb:75 0.013
Tags: @product @automatic_upgrade
5:58.101
Before features/support/hooks.rb:245 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.787
And no SquashFS delta is installed 0.108
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.105
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.422
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.561
When the network is plugged 0.111
And Tor is ready 17.285
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.667
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.869
Given I shutdown Tails and wait for the computer to power off 6.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.351
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.808
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.456
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.323
# 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.421
When the network is plugged 0.040
And Tor is ready 14.714
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.748
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.151
Given I shutdown Tails and wait for the computer to power off 4.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.462
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 2.206
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.547
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.067
# 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.294
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.413
When the network is plugged 0.041
And Tor is ready 18.793
Then the Upgrader considers the system as up-to-date 0.306
# 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 30.342
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.520
After features/support/hooks.rb:291 0.833
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
30.555
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.434
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.345
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.082
And the signing key used by the Upgrader is outdated 0.610
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 17.331
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.699
After features/support/hooks.rb:291 0.749
After features/support/hooks.rb:75 0.000