Project Number Date
test_Tails_ISO_stable 4682 26 Feb 2024, 12:25

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:29.675 Passed
6:0.503
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.486
And no SquashFS delta is installed 0.391
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 1.503
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.085
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.499
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.643
When the network is plugged 0.341
And Tor is ready 17.260
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.839
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 10.473
Given I shutdown Tails and wait for the computer to power off 6.491
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.301
Then Tails is running version 2.2~testoverlayfsng 0.162
And all tps features are active 2.555
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.424
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.328
# 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.341
When the network is plugged 0.048
And Tor is ready 16.669
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.696
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.192
Given I shutdown Tails and wait for the computer to power off 4.443
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.700
Then Tails is running version 2.3~testoverlayfsng 0.159
And all tps features are active 2.277
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.786
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.108
# 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.329
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.337
When the network is plugged 0.035
And Tor is ready 19.592
Then the Upgrader considers the system as up-to-date 0.267
# 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 27.226
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.428
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.021
29.172
Before features/support/hooks.rb:245 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.038
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.448
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.075
And the signing key used by the Upgrader is outdated 0.691
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 13.861
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.013
After features/support/hooks.rb:291 0.710
After features/support/hooks.rb:75 0.000