Project Number Date
test_Tails_ISO_devel 3192 13 Dec 2023, 12:14

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:0.902 Passed
5:35.018
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.022
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.292
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.412
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.519
When the network is plugged 0.065
And Tor is ready 14.884
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.652
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.040
Given I shutdown Tails and wait for the computer to power off 5.281
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:46.045
Then Tails is running version 2.2~testoverlayfsng 0.097
And all tps features are active 2.443
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.391
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.305
# 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.284
When the network is plugged 0.061
And Tor is ready 12.912
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.847
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.652
Given I shutdown Tails and wait for the computer to power off 3.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.532
Then Tails is running version 2.3~testoverlayfsng 0.115
And all tps features are active 2.172
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.608
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.090
# 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.265
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.334
When the network is plugged 0.043
And Tor is ready 14.073
Then the Upgrader considers the system as up-to-date 0.299
# 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 27.305
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.373
After features/support/hooks.rb:291 0.790
After features/support/hooks.rb:75 0.019
25.883
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.709
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.445
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.065
And the signing key used by the Upgrader is outdated 0.550
But a current signing key is available on our website 0.000
When the network is plugged 0.043
And Tor is ready 13.425
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.642
After features/support/hooks.rb:291 0.701
After features/support/hooks.rb:75 0.000