Project Number Date
test_Tails_ISO_devel 3218 31 Dec 2023, 12:12

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:18.893 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:19.164
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 17.296
When I start Tails from USB drive "old" with network unplugged 56.672
Then the boot device has safe access rights 3.005
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.225
And I unplug USB drive "old" 0.211
After features/support/hooks.rb:291 3.523
After features/support/hooks.rb:75 0.011
Tags: @product
1:56.897
Before features/support/hooks.rb:245 0.007
Given a computer 0.240
And I start Tails from USB drive "old" with network unplugged and I login 1:2.680
Then Tails is running from USB drive "old" 0.446
And I create a persistent partition 44.133
And I take note of which tps features are available 1.514
Then a Tails persistence partition exists on USB drive "old" 0.797
And I shutdown Tails and wait for the computer to power off 7.084
After features/support/hooks.rb:291 0.143
After features/support/hooks.rb:75 0.009
Tags: @product
2:21.101
Before features/support/hooks.rb:245 0.005
Given a computer 0.198
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.396
Then Tails is running from USB drive "old" 0.325
And all tps features are active 2.114
When I write some files expected to persist 1.784
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.291
And all persistence configuration files have safe access rights 0.653
And all persistent directories from the old Tails version have safe access rights 2.771
And I take note of which tps features are available 0.558
And I shutdown Tails and wait for the computer to power off 3.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.935
After features/support/hooks.rb:291 0.113
After features/support/hooks.rb:75 0.012
Tags: @product
2:38.130
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 11.661
And I log in to a new session 18.685
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.085
And I plug USB drive "to_upgrade" 2.499
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.895
Then the running Tails is installed on USB drive "to_upgrade" 12.930
And I unplug USB drive "to_upgrade" 0.195
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 6.723
After features/support/hooks.rb:75 0.000
Tags: @product
1:55.111
Before features/support/hooks.rb:245 0.007
Given a computer 0.193
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:44.898
Then all tps features from the old Tails version are active 1.599
And Tails is running from USB drive "to_upgrade" 0.355
And the boot device has safe access rights 3.292
And the expected persistent files created with the old Tails version are present in the filesystem 1.726
And all persistent directories from the old Tails version have safe access rights 3.045
After features/support/hooks.rb:291 0.661
After features/support/hooks.rb:75 0.025
Tags: @product @automatic_upgrade
5:39.123
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 10.733
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.368
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.061
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.404
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.570
When the network is plugged 0.039
And Tor is ready 15.606
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.719
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.652
Given I shutdown Tails and wait for the computer to power off 6.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.640
Then Tails is running version 2.2~testoverlayfsng 0.094
And all tps features are active 2.231
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.386
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.105
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.259
# 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.302
When the network is plugged 0.036
And Tor is ready 18.070
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.629
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.708
Given I shutdown Tails and wait for the computer to power off 4.061
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.895
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 1.992
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.565
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.298
When the network is plugged 0.047
And Tor is ready 14.871
Then the Upgrader considers the system as up-to-date 0.263
# 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.253
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.304
After features/support/hooks.rb:291 0.730
After features/support/hooks.rb:75 0.019
Tags: @product @automatic_upgrade
29.364
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.552
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.422
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the signing key used by the Upgrader is outdated 0.496
But a current signing key is available on our website 0.000
When the network is plugged 0.045
And Tor is ready 16.001
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.774
After features/support/hooks.rb:291 1.035
After features/support/hooks.rb:75 0.000