Project Number Date
test_Tails_ISO_stable 4593 27 Dec 2023, 12:28

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:38.955 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:38.487
Before features/support/hooks.rb:245 0.009
Given a computer 0.192
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 27.380
When I start Tails from USB drive "old" with network unplugged 1:5.556
Then the boot device has safe access rights 3.341
And Tails is running from USB drive "old" 0.348
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.185
After features/support/hooks.rb:291 3.520
After features/support/hooks.rb:75 0.009
Tags: @product
2:12.364
Before features/support/hooks.rb:245 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login 1:16.625
Then Tails is running from USB drive "old" 0.483
And I create a persistent partition 45.410
And I take note of which tps features are available 1.582
Then a Tails persistence partition exists on USB drive "old" 0.883
And I shutdown Tails and wait for the computer to power off 7.150
After features/support/hooks.rb:291 0.119
After features/support/hooks.rb:75 0.010
Tags: @product
2:25.007
Before features/support/hooks.rb:245 0.007
Given a computer 0.177
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:56.575
Then Tails is running from USB drive "old" 0.379
And all tps features are active 2.218
When I write some files expected to persist 1.806
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.618
And all persistent directories from the old Tails version have safe access rights 2.846
And I take note of which tps features are available 0.478
And I shutdown Tails and wait for the computer to power off 3.069
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.613
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.324
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.266
And I log in to a new session 17.552
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.349
And I plug USB drive "to_upgrade" 2.554
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:50.665
Then the running Tails is installed on USB drive "to_upgrade" 14.462
And I unplug USB drive "to_upgrade" 0.259
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:291 1.862
After features/support/hooks.rb:75 0.000
Tags: @product
2:5.068
Before features/support/hooks.rb:245 0.009
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:53.581
Then all tps features from the old Tails version are active 2.084
And Tails is running from USB drive "to_upgrade" 0.402
And the boot device has safe access rights 3.871
And the expected persistent files created with the old Tails version are present in the filesystem 2.060
And all persistent directories from the old Tails version have safe access rights 2.872
After features/support/hooks.rb:291 0.916
After features/support/hooks.rb:75 0.009
Tags: @product @automatic_upgrade
6:12.978
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 12.302
And no SquashFS delta is installed 0.112
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.339
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.085
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.436
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.579
When the network is plugged 0.046
And Tor is ready 15.802
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.974
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.127
Given I shutdown Tails and wait for the computer to power off 10.438
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.767
Then Tails is running version 2.2~testoverlayfsng 0.268
And all tps features are active 4.664
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.413
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.300
# 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.339
When the network is plugged 0.042
And Tor is ready 17.220
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.711
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.162
Given I shutdown Tails and wait for the computer to power off 4.297
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.156
Then Tails is running version 2.3~testoverlayfsng 0.120
And all tps features are active 2.794
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.579
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.078
# 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.286
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.290
When the network is plugged 0.103
And Tor is ready 15.146
Then the Upgrader considers the system as up-to-date 10.712
# 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 30.906
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.297
After features/support/hooks.rb:291 0.748
After features/support/hooks.rb:75 0.036
Tags: @product @automatic_upgrade
27.724
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.372
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.052
And the signing key used by the Upgrader is outdated 0.418
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 15.462
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.605
After features/support/hooks.rb:291 1.467
After features/support/hooks.rb:75 0.000