Project Number Date
test_Tails_ISO_stable 4574 18 Dec 2023, 15:29

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:10.904 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.339
Before features/support/hooks.rb:245 0.006
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 26.315
When I start Tails from USB drive "old" with network unplugged 58.798
Then the boot device has safe access rights 3.017
And Tails is running from USB drive "old" 0.323
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.278
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:291 3.492
After features/support/hooks.rb:75 0.012
Tags: @product
2:3.175
Before features/support/hooks.rb:245 0.007
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login 1:6.164
Then Tails is running from USB drive "old" 0.444
And I create a persistent partition 43.964
And I take note of which tps features are available 2.216
Then a Tails persistence partition exists on USB drive "old" 0.953
And I shutdown Tails and wait for the computer to power off 9.250
After features/support/hooks.rb:291 0.154
After features/support/hooks.rb:75 0.010
Tags: @product
2:26.440
Before features/support/hooks.rb:245 0.006
Given a computer 0.200
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:57.735
Then Tails is running from USB drive "old" 0.373
And all tps features are active 2.356
When I write some files expected to persist 1.954
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.268
And all persistence configuration files have safe access rights 0.656
And all persistent directories from the old Tails version have safe access rights 3.014
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 3.110
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.270
After features/support/hooks.rb:291 0.169
After features/support/hooks.rb:75 0.008
Tags: @product
2:33.731
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 9.898
And I log in to a new session 19.167
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.216
And I plug USB drive "to_upgrade" 2.517
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.167
Then the running Tails is installed on USB drive "to_upgrade" 12.380
And I unplug USB drive "to_upgrade" 0.206
And I unplug USB drive "__internal" 0.177
After features/support/hooks.rb:291 3.614
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.823
Before features/support/hooks.rb:245 0.007
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.358
Then all tps features from the old Tails version are active 1.781
And Tails is running from USB drive "to_upgrade" 0.411
And the boot device has safe access rights 4.073
And the expected persistent files created with the old Tails version are present in the filesystem 1.893
And all persistent directories from the old Tails version have safe access rights 3.079
After features/support/hooks.rb:291 0.852
After features/support/hooks.rb:75 0.012
Tags: @product @automatic_upgrade
6:4.542
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.890
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.390
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.482
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.599
When the network is plugged 0.063
And Tor is ready 20.279
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.731
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.404
Given I shutdown Tails and wait for the computer to power off 6.444
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.342
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.299
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.420
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.298
# 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.316
When the network is plugged 0.073
And Tor is ready 14.707
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.731
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.873
Given I shutdown Tails and wait for the computer to power off 4.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.640
Then Tails is running version 2.3~testoverlayfsng 0.114
And all tps features are active 2.253
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.639
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.073
# 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.322
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.354
When the network is plugged 0.040
And Tor is ready 17.120
Then the Upgrader considers the system as up-to-date 0.289
# 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.965
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.538
After features/support/hooks.rb:291 1.032
After features/support/hooks.rb:75 0.023
Tags: @product @automatic_upgrade
27.852
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.966
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.435
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the signing key used by the Upgrader is outdated 1.263
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 13.369
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.725
After features/support/hooks.rb:291 0.871
After features/support/hooks.rb:75 0.000