Project Number Date
test_Tails_ISO_stable 4601 04 Jan 2024, 12:10

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:51.234 Passed
5:59.087
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.178
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.305
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.095
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.389
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.539
When the network is plugged 0.045
And Tor is ready 17.075
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.664
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.296
Given I shutdown Tails and wait for the computer to power off 5.429
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.926
Then Tails is running version 2.2~testoverlayfsng 0.130
And all tps features are active 2.339
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.402
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.291
# 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.310
When the network is plugged 0.033
And Tor is ready 15.114
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 4.100
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.563
Given I shutdown Tails and wait for the computer to power off 4.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:53.512
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 2.258
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.654
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.059
# 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 1.294
When the network is plugged 0.038
And Tor is ready 20.813
Then the Upgrader considers the system as up-to-date 0.281
# 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 24.663
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.348
After features/support/hooks.rb:291 0.810
After features/support/hooks.rb:75 0.019
52.146
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.914
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.057
And the signing key used by the Upgrader is outdated 0.523
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 40.634
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.688
After features/support/hooks.rb:291 0.809
After features/support/hooks.rb:75 0.000