Project Number Date
test_Tails_ISO_devel 3241 18 Jan 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:2.768 Passed
5:37.234
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.699
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.291
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.333
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.475
When the network is plugged 0.020
And Tor is ready 15.169
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.604
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.326
Given I shutdown Tails and wait for the computer to power off 5.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.708
Then Tails is running version 2.2~testoverlayfsng 0.089
And all tps features are active 1.725
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.303
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.255
# 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.260
When the network is plugged 0.030
And Tor is ready 15.788
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.554
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.566
Given I shutdown Tails and wait for the computer to power off 4.140
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.809
Then Tails is running version 2.3~testoverlayfsng 0.086
And all tps features are active 1.702
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.564
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.083
# 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.275
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.303
When the network is plugged 0.027
And Tor is ready 13.303
Then the Upgrader considers the system as up-to-date 10.680
# 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.804
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.712
After features/support/hooks.rb:291 0.756
After features/support/hooks.rb:75 0.020
25.533
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 9.379
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.259
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.047
And the signing key used by the Upgrader is outdated 1.001
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 13.126
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.693
After features/support/hooks.rb:291 0.657
After features/support/hooks.rb:75 0.000