Project Number Date
test_Tails_ISO_stable 4577 19 Dec 2023, 12:09

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:47.089 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:23.211
Before features/support/hooks.rb:245 0.024
Given a computer 0.182
And I create a 7200 MiB disk named "old" 0.077
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 20.371
When I start Tails from USB drive "old" with network unplugged 57.494
Then the boot device has safe access rights 3.175
And Tails is running from USB drive "old" 0.286
And there is no persistence partition on USB drive "old" 0.058
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:291 3.714
After features/support/hooks.rb:75 0.008
Tags: @product
1:56.215
Before features/support/hooks.rb:245 0.004
Given a computer 0.241
And I start Tails from USB drive "old" with network unplugged and I login 1:3.040
Then Tails is running from USB drive "old" 0.541
And I create a persistent partition 43.073
And I take note of which tps features are available 1.440
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.085
After features/support/hooks.rb:291 0.174
After features/support/hooks.rb:75 0.011
Tags: @product
2:20.020
Before features/support/hooks.rb:245 0.006
Given a computer 0.236
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:53.313
Then Tails is running from USB drive "old" 0.318
And all tps features are active 2.201
When I write some files expected to persist 1.871
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.309
And all persistence configuration files have safe access rights 0.677
And all persistent directories from the old Tails version have safe access rights 2.618
And I take note of which tps features are available 0.524
And I shutdown Tails and wait for the computer to power off 3.073
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.876
After features/support/hooks.rb:291 0.097
After features/support/hooks.rb:75 0.009
Tags: @product
2:30.076
Before features/support/hooks.rb:245 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.310
And I log in to a new session 15.939
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.157
And I plug USB drive "to_upgrade" 2.398
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.565
Then the running Tails is installed on USB drive "to_upgrade" 12.295
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:291 1.923
After features/support/hooks.rb:75 0.000
Tags: @product
2:0.895
Before features/support/hooks.rb:245 0.007
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.143
Then all tps features from the old Tails version are active 1.698
And Tails is running from USB drive "to_upgrade" 0.345
And the boot device has safe access rights 3.284
And the expected persistent files created with the old Tails version are present in the filesystem 1.623
And all persistent directories from the old Tails version have safe access rights 2.631
After features/support/hooks.rb:291 0.712
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:9.631
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 10.569
And no SquashFS delta is installed 0.105
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.056
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.541
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.503
When the network is plugged 0.045
And Tor is ready 15.400
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.565
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.866
Given I shutdown Tails and wait for the computer to power off 6.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.683
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.185
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.376
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.308
When the network is plugged 0.066
And Tor is ready 16.653
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.666
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.881
Given I shutdown Tails and wait for the computer to power off 4.125
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.078
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 3.992
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.069
# 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.308
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.314
When the network is plugged 0.158
And Tor is ready 43.357
Then the Upgrader considers the system as up-to-date 0.274
# 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.684
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.071
After features/support/hooks.rb:291 0.937
After features/support/hooks.rb:75 0.018
Tags: @product @automatic_upgrade
27.038
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 9.731
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.350
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.632
But a current signing key is available on our website 0.000
When the network is plugged 0.056
And Tor is ready 13.624
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.569
After features/support/hooks.rb:291 1.000
After features/support/hooks.rb:75 0.000