Project Number Date
test_Tails_ISO_stable 4566 13 Dec 2023, 12:11

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:33.265 Passed
6:4.913
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 10.896
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.310
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.103
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.468
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.633
When the network is plugged 0.037
And Tor is ready 17.099
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.797
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.621
Given I shutdown Tails and wait for the computer to power off 6.651
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:50.363
Then Tails is running version 2.2~testoverlayfsng 0.100
And all tps features are active 2.200
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.409
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.102
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.275
# 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.395
When the network is plugged 0.036
And Tor is ready 15.485
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.687
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.015
Given I shutdown Tails and wait for the computer to power off 4.321
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.199
Then Tails is running version 2.3~testoverlayfsng 0.114
And all tps features are active 2.398
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.640
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.102
# 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.348
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.413
When the network is plugged 0.042
And Tor is ready 15.550
Then the Upgrader considers the system as up-to-date 0.432
# 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.910
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.617
After features/support/hooks.rb:291 0.987
After features/support/hooks.rb:75 0.018
28.352
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.595
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.365
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.585
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 15.107
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.608
After features/support/hooks.rb:291 0.635
After features/support/hooks.rb:75 0.000