Project Number Date
test_Tails_ISO_stable 4588 24 Dec 2023, 12:04

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:54.352 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:41.227
Before features/support/hooks.rb:245 0.005
Given a computer 0.175
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.047
And I write an old version of the Tails USB image to disk "old" 19.025
When I start Tails from USB drive "old" with network unplugged 1:17.195
Then the boot device has safe access rights 2.848
And Tails is running from USB drive "old" 0.299
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.261
And I unplug USB drive "old" 0.184
After features/support/hooks.rb:291 3.434
After features/support/hooks.rb:75 0.009
Tags: @product
1:55.979
Before features/support/hooks.rb:245 0.005
Given a computer 0.166
And I start Tails from USB drive "old" with network unplugged and I login 1:3.834
Then Tails is running from USB drive "old" 0.460
And I create a persistent partition 42.161
And I take note of which tps features are available 1.429
Then a Tails persistence partition exists on USB drive "old" 0.851
And I shutdown Tails and wait for the computer to power off 7.074
After features/support/hooks.rb:291 0.102
After features/support/hooks.rb:75 0.009
Tags: @product
2:12.194
Before features/support/hooks.rb:245 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:46.324
Then Tails is running from USB drive "old" 0.331
And all tps features are active 1.991
When I write some files expected to persist 1.715
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.520
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.517
And I shutdown Tails and wait for the computer to power off 3.070
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.734
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.008
Tags: @product
2:30.992
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.506
And I log in to a new session 16.785
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.225
And I plug USB drive "to_upgrade" 2.416
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.378
Then the running Tails is installed on USB drive "to_upgrade" 12.303
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.178
After features/support/hooks.rb:291 1.858
After features/support/hooks.rb:75 0.000
Tags: @product
2:4.410
Before features/support/hooks.rb:245 0.006
Given a computer 0.213
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:54.390
Then all tps features from the old Tails version are active 1.591
And Tails is running from USB drive "to_upgrade" 0.437
And the boot device has safe access rights 3.605
And the expected persistent files created with the old Tails version are present in the filesystem 1.749
And all persistent directories from the old Tails version have safe access rights 2.421
After features/support/hooks.rb:291 0.678
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:3.023
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.380
And no SquashFS delta is installed 0.147
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.300
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.088
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.460
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.645
When the network is plugged 0.043
And Tor is ready 16.790
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.651
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.756
Given I shutdown Tails and wait for the computer to power off 7.290
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.404
Then Tails is running version 2.2~testoverlayfsng 0.100
And all tps features are active 2.494
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.375
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.268
# 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.311
When the network is plugged 0.039
And Tor is ready 13.906
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.738
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.477
Given I shutdown Tails and wait for the computer to power off 4.319
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.807
Then Tails is running version 2.3~testoverlayfsng 0.095
And all tps features are active 2.009
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.598
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.072
# 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.277
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.286
When the network is plugged 0.034
And Tor is ready 17.037
Then the Upgrader considers the system as up-to-date 0.251
# 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.215
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.278
After features/support/hooks.rb:291 0.810
After features/support/hooks.rb:75 0.022
Tags: @product @automatic_upgrade
26.526
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.780
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.419
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 0.462
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 12.063
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.689
After features/support/hooks.rb:291 0.725
After features/support/hooks.rb:75 0.000