Project Number Date
test_Tails_ISO_stable 4646 30 Jan 2024, 12:57

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:29.511 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:42.023
Before features/support/hooks.rb:245 0.006
Given a computer 0.237
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.064
And I write an old version of the Tails USB image to disk "old" 27.607
When I start Tails from USB drive "old" with network unplugged 1:8.680
Then the boot device has safe access rights 3.254
And Tails is running from USB drive "old" 0.296
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.288
And I unplug USB drive "old" 0.396
After features/support/hooks.rb:291 3.497
After features/support/hooks.rb:75 0.012
Tags: @product
1:58.779
Before features/support/hooks.rb:245 0.008
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:5.083
Then Tails is running from USB drive "old" 0.437
And I create a persistent partition 43.745
And I take note of which tps features are available 1.450
Then a Tails persistence partition exists on USB drive "old" 0.790
And I shutdown Tails and wait for the computer to power off 7.071
After features/support/hooks.rb:291 0.108
After features/support/hooks.rb:75 0.009
Tags: @product
2:14.750
Before features/support/hooks.rb:245 0.007
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:47.808
Then Tails is running from USB drive "old" 0.382
And all tps features are active 2.271
When I write some files expected to persist 2.002
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.229
And all persistence configuration files have safe access rights 0.414
And all persistent directories from the old Tails version have safe access rights 2.946
And I take note of which tps features are available 0.507
And I shutdown Tails and wait for the computer to power off 3.064
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.938
After features/support/hooks.rb:291 0.102
After features/support/hooks.rb:75 0.010
Tags: @product
2:34.467
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 9.967
And I log in to a new session 18.207
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.118
And I plug USB drive "to_upgrade" 2.462
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.343
Then the running Tails is installed on USB drive "to_upgrade" 13.954
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.189
After features/support/hooks.rb:291 0.776
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.937
Before features/support/hooks.rb:245 0.008
Given a computer 0.215
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.204
Then all tps features from the old Tails version are active 1.858
And Tails is running from USB drive "to_upgrade" 0.392
And the boot device has safe access rights 3.524
And the expected persistent files created with the old Tails version are present in the filesystem 1.821
And all persistent directories from the old Tails version have safe access rights 2.920
After features/support/hooks.rb:291 0.718
After features/support/hooks.rb:75 0.034
Tags: @product @automatic_upgrade
6:30.839
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.051
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.375
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.708
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.634
When the network is plugged 0.030
And Tor is ready 15.973
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.819
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 33.972
Given I shutdown Tails and wait for the computer to power off 6.139
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.019
Then Tails is running version 2.2~testoverlayfsng 0.097
And all tps features are active 2.442
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.522
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.331
# 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.336
When the network is plugged 0.055
And Tor is ready 14.979
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.003
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.718
Given I shutdown Tails and wait for the computer to power off 5.555
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.033
Then Tails is running version 2.3~testoverlayfsng 0.106
And all tps features are active 2.228
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.745
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.347
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.314
When the network is plugged 0.061
And Tor is ready 17.671
Then the Upgrader considers the system as up-to-date 0.308
# 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 28.486
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.415
After features/support/hooks.rb:291 0.872
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
29.714
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 10.290
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.094
And the signing key used by the Upgrader is outdated 0.643
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 15.328
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.946
After features/support/hooks.rb:291 1.252
After features/support/hooks.rb:75 0.000