Project Number Date
test_Tails_ISO_stable 4635 24 Jan 2024, 23:52

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:57.628 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:27.480
Before features/support/hooks.rb:245 0.005
Given a computer 0.131
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 22.897
When I start Tails from USB drive "old" with network unplugged 58.630
Then the boot device has safe access rights 3.803
And Tails is running from USB drive "old" 0.333
And there is no persistence partition on USB drive "old" 0.074
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.292
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 3.668
After features/support/hooks.rb:75 0.009
Tags: @product
1:55.635
Before features/support/hooks.rb:245 0.006
Given a computer 0.141
And I start Tails from USB drive "old" with network unplugged and I login 1:4.084
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 41.808
And I take note of which tps features are available 1.420
Then a Tails persistence partition exists on USB drive "old" 0.792
And I shutdown Tails and wait for the computer to power off 7.061
After features/support/hooks.rb:291 0.128
After features/support/hooks.rb:75 0.010
Tags: @product
2:16.516
Before features/support/hooks.rb:245 0.006
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.107
Then Tails is running from USB drive "old" 0.319
And all tps features are active 1.706
When I write some files expected to persist 1.821
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.437
And all persistent directories from the old Tails version have safe access rights 2.672
And I take note of which tps features are available 0.311
And I shutdown Tails and wait for the computer to power off 3.066
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.688
After features/support/hooks.rb:291 0.144
After features/support/hooks.rb:75 0.008
Tags: @product
2:29.350
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 11.118
And I log in to a new session 15.170
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.190
And I plug USB drive "to_upgrade" 2.506
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:46.959
Then the running Tails is installed on USB drive "to_upgrade" 12.006
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:291 1.013
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.576
Before features/support/hooks.rb:245 0.006
Given a computer 0.240
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:52.018
Then all tps features from the old Tails version are active 1.533
And Tails is running from USB drive "to_upgrade" 0.352
And the boot device has safe access rights 3.685
And the expected persistent files created with the old Tails version are present in the filesystem 1.825
And all persistent directories from the old Tails version have safe access rights 2.920
After features/support/hooks.rb:291 0.639
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
5:51.322
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 11.059
And no SquashFS delta is installed 0.130
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.285
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.057
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.463
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.542
When the network is plugged 0.023
And Tor is ready 15.711
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.709
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.166
Given I shutdown Tails and wait for the computer to power off 5.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.083
Then Tails is running version 2.2~testoverlayfsng 0.112
And all tps features are active 1.846
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.443
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.279
# 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.289
When the network is plugged 0.031
And Tor is ready 16.648
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.676
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.907
Given I shutdown Tails and wait for the computer to power off 4.286
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.662
Then Tails is running version 2.3~testoverlayfsng 0.124
And all tps features are active 2.048
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.616
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.085
# 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.262
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.294
When the network is plugged 0.033
And Tor is ready 19.789
Then the Upgrader considers the system as up-to-date 0.229
# 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 26.358
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.778
After features/support/hooks.rb:291 0.740
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
54.744
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.270
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.366
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 0.481
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 43.954
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.573
After features/support/hooks.rb:291 0.881
After features/support/hooks.rb:75 0.000