Project Number Date
test_Tails_ISO_stable 4636 25 Jan 2024, 15:05

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 7:6.481 Passed
6:35.960
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.386
And no SquashFS delta is installed 0.313
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.531
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.550
When the network is plugged 0.038
And Tor is ready 44.437
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.611
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.137
Given I shutdown Tails and wait for the computer to power off 6.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.114
Then Tails is running version 2.2~testoverlayfsng 0.135
And all tps features are active 2.498
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.363
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.269
# 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.380
When the network is plugged 0.050
And Tor is ready 14.597
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.602
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.403
Given I shutdown Tails and wait for the computer to power off 4.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.331
Then Tails is running version 2.3~testoverlayfsng 0.140
And all tps features are active 2.101
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.691
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.070
# 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.307
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.338
When the network is plugged 0.038
And Tor is ready 15.988
Then the Upgrader considers the system as up-to-date 0.314
# 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 26.623
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.336
After features/support/hooks.rb:291 0.773
After features/support/hooks.rb:75 0.017
30.520
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.606
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.428
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.102
And the signing key used by the Upgrader is outdated 0.506
But a current signing key is available on our website 0.000
When the network is plugged 0.127
And Tor is ready 17.849
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.900
After features/support/hooks.rb:291 0.761
After features/support/hooks.rb:75 0.000