Project Number Date
test_Tails_ISO_stable 4599 02 Jan 2024, 12:06

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:24.688 Passed
5:56.370
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.889
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.352
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.051
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.436
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.645
When the network is plugged 0.045
And Tor is ready 16.700
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.791
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.109
Given I shutdown Tails and wait for the computer to power off 10.295
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.115
Then Tails is running version 2.2~testoverlayfsng 0.113
And all tps features are active 2.349
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.406
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.074
# 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.288
When the network is plugged 0.051
And Tor is ready 15.149
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.721
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.125
Given I shutdown Tails and wait for the computer to power off 5.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.775
Then Tails is running version 2.3~testoverlayfsng 0.094
And all tps features are active 2.140
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.569
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.104
# 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.299
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.280
When the network is plugged 0.046
And Tor is ready 16.969
Then the Upgrader considers the system as up-to-date 0.277
# 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.764
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.365
After features/support/hooks.rb:291 0.758
After features/support/hooks.rb:75 0.032
28.317
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.923
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.362
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.083
And the signing key used by the Upgrader is outdated 1.089
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 15.217
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.594
After features/support/hooks.rb:291 0.638
After features/support/hooks.rb:75 0.000