Project Number Date
test_Tails_ISO_devel 3235 13 Jan 2024, 12:23

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:4.551 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.896
Before features/support/hooks.rb:245 0.008
Given a computer 0.220
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 19.078
When I start Tails from USB drive "old" with network unplugged 1:5.780
Then the boot device has safe access rights 3.640
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.082
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.214
After features/support/hooks.rb:291 3.602
After features/support/hooks.rb:75 0.009
Tags: @product
1:58.565
Before features/support/hooks.rb:245 0.007
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login 1:6.718
Then Tails is running from USB drive "old" 0.400
And I create a persistent partition 42.673
And I take note of which tps features are available 1.458
Then a Tails persistence partition exists on USB drive "old" 0.905
And I shutdown Tails and wait for the computer to power off 6.177
After features/support/hooks.rb:291 0.130
After features/support/hooks.rb:75 0.012
Tags: @product
2:20.834
Before features/support/hooks.rb:245 0.010
Given a computer 0.261
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:52.900
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.428
When I write some files expected to persist 1.956
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.747
And all persistent directories from the old Tails version have safe access rights 3.196
And I take note of which tps features are available 0.693
And I shutdown Tails and wait for the computer to power off 3.089
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.849
After features/support/hooks.rb:291 0.103
After features/support/hooks.rb:75 0.013
Tags: @product
2:59.253
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 35.192
And I log in to a new session 17.021
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.221
And I plug USB drive "to_upgrade" 2.490
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:49.463
Then the running Tails is installed on USB drive "to_upgrade" 13.499
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 8.843
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.693
Before features/support/hooks.rb:245 0.007
Given a computer 0.226
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:47.509
Then all tps features from the old Tails version are active 1.867
And Tails is running from USB drive "to_upgrade" 0.393
And the boot device has safe access rights 3.982
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.033
After features/support/hooks.rb:291 0.640
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
5:48.899
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.203
And no SquashFS delta is installed 0.133
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.337
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.483
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.577
When the network is plugged 0.039
And Tor is ready 20.029
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.679
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.861
Given I shutdown Tails and wait for the computer to power off 5.065
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.268
Then Tails is running version 2.2~testoverlayfsng 0.099
And all tps features are active 2.146
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.338
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.276
# 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.321
When the network is plugged 0.040
And Tor is ready 15.615
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.674
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.327
Given I shutdown Tails and wait for the computer to power off 4.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.537
Then Tails is running version 2.3~testoverlayfsng 0.119
And all tps features are active 2.088
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.586
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.079
# 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.282
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.373
When the network is plugged 0.061
And Tor is ready 13.900
Then the Upgrader considers the system as up-to-date 0.338
# 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 27.398
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.395
After features/support/hooks.rb:291 1.006
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
27.409
Before features/support/hooks.rb:245 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.966
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.294
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.073
And the signing key used by the Upgrader is outdated 0.799
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 13.482
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.755
After features/support/hooks.rb:291 1.018
After features/support/hooks.rb:75 0.000