Project Number Date
test_Tails_ISO_devel 3227 09 Jan 2024, 12:27

Tag Report

Steps Scenarios Features
Tag Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
@automatic_upgrade 43 0 0 0 0 43 2 0 2 6:8.160 Passed
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
5:41.230
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.330
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.281
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.067
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.359
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.518
When the network is plugged 0.036
And Tor is ready 18.615
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.667
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.784
Given I shutdown Tails and wait for the computer to power off 6.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.406
Then Tails is running version 2.2~testoverlayfsng 0.102
And all tps features are active 2.123
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.359
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.278
# 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.329
When the network is plugged 0.033
And Tor is ready 16.188
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.577
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.514
Given I shutdown Tails and wait for the computer to power off 4.146
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.254
Then Tails is running version 2.3~testoverlayfsng 0.115
And all tps features are active 2.131
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.619
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.074
# 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.302
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.302
When the network is plugged 0.050
And Tor is ready 14.590
Then the Upgrader considers the system as up-to-date 0.255
# 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.651
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.584
After features/support/hooks.rb:291 0.769
After features/support/hooks.rb:75 0.028
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
26.930
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.639
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.058
And the signing key used by the Upgrader is outdated 0.961
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 13.275
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.621
After features/support/hooks.rb:291 0.688
After features/support/hooks.rb:75 0.000