Project Number Date
test_Tails_ISO_devel 3208 23 Dec 2023, 12:24

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:24.126 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:24.195
Before features/support/hooks.rb:245 0.005
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.043
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 20.485
When I start Tails from USB drive "old" with network unplugged 58.274
Then the boot device has safe access rights 3.260
And Tails is running from USB drive "old" 0.279
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 3.698
After features/support/hooks.rb:75 0.011
Tags: @product
1:56.727
Before features/support/hooks.rb:245 0.007
Given a computer 0.206
And I start Tails from USB drive "old" with network unplugged and I login 1:3.724
Then Tails is running from USB drive "old" 0.539
And I create a persistent partition 42.737
And I take note of which tps features are available 1.572
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 7.074
After features/support/hooks.rb:291 0.159
After features/support/hooks.rb:75 0.010
Tags: @product
2:14.678
Before features/support/hooks.rb:245 0.005
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.986
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.364
When I write some files expected to persist 1.855
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.622
And all persistent directories from the old Tails version have safe access rights 2.700
And I take note of which tps features are available 0.574
And I shutdown Tails and wait for the computer to power off 3.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.732
After features/support/hooks.rb:291 0.117
After features/support/hooks.rb:75 0.010
Tags: @product
2:36.277
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.897
And I log in to a new session 17.548
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.217
And I plug USB drive "to_upgrade" 2.512
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.653
Then the running Tails is installed on USB drive "to_upgrade" 13.056
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 6.924
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.337
Before features/support/hooks.rb:245 0.008
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:46.563
Then all tps features from the old Tails version are active 1.573
And Tails is running from USB drive "to_upgrade" 0.314
And the boot device has safe access rights 3.411
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.734
After features/support/hooks.rb:291 0.699
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
5:47.526
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 13.274
And no SquashFS delta is installed 0.095
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.340
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.053
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.377
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.545
When the network is plugged 0.062
And Tor is ready 18.406
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.662
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.014
Given I shutdown Tails and wait for the computer to power off 6.197
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.742
Then Tails is running version 2.2~testoverlayfsng 0.111
And all tps features are active 2.275
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.448
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.408
# 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.470
When the network is plugged 0.087
And Tor is ready 17.794
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.672
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.121
Given I shutdown Tails and wait for the computer to power off 3.089
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.427
Then Tails is running version 2.3~testoverlayfsng 0.107
And all tps features are active 2.190
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.709
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.103
# 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.290
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.309
When the network is plugged 0.050
And Tor is ready 13.135
Then the Upgrader considers the system as up-to-date 10.817
# 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 25.440
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.617
After features/support/hooks.rb:291 0.987
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
28.382
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 9.629
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 signing key used by the Upgrader is outdated 0.527
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 14.954
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.840
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.000