Project Number Date
test_Tails_ISO_stable 4633 24 Jan 2024, 16:22

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:59.853 Passed
6:29.142
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.755
And no SquashFS delta is installed 0.111
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.284
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.426
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.619
When the network is plugged 0.033
And Tor is ready 46.757
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.624
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 11.507
Given I shutdown Tails and wait for the computer to power off 7.379
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.130
Then Tails is running version 2.2~testoverlayfsng 0.121
And all tps features are active 2.239
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.414
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.123
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.330
# 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.299
When the network is plugged 0.046
And Tor is ready 16.274
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.085
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.761
Given I shutdown Tails and wait for the computer to power off 4.375
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.322
Then Tails is running version 2.3~testoverlayfsng 0.189
And all tps features are active 2.069
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.075
# 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.340
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.448
When the network is plugged 0.044
And Tor is ready 16.396
Then the Upgrader considers the system as up-to-date 0.328
# 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.201
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.378
After features/support/hooks.rb:291 0.825
After features/support/hooks.rb:75 0.038
30.710
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.011
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.072
And the signing key used by the Upgrader is outdated 1.225
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 14.421
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.605
After features/support/hooks.rb:291 1.074
After features/support/hooks.rb:75 0.000