Project Number Date
test_Tails_ISO_devel 3243 19 Jan 2024, 13:28

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:51.968 Passed
6:22.778
Before features/support/hooks.rb:245 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.897
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.340
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.050
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.407
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.671
When the network is plugged 0.032
And Tor is ready 47.130
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.613
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.259
Given I shutdown Tails and wait for the computer to power off 6.074
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.810
Then Tails is running version 2.2~testoverlayfsng 0.143
And all tps features are active 2.442
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.461
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.088
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.350
# 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.403
When the network is plugged 0.041
And Tor is ready 17.165
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.721
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.629
Given I shutdown Tails and wait for the computer to power off 4.200
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.675
Then Tails is running version 2.3~testoverlayfsng 0.149
And all tps features are active 2.157
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.652
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.081
# 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.351
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.392
When the network is plugged 0.035
And Tor is ready 17.993
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.554
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.778
After features/support/hooks.rb:75 0.021
29.189
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.297
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.278
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.094
And the signing key used by the Upgrader is outdated 0.626
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 14.991
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.856
After features/support/hooks.rb:291 0.819
After features/support/hooks.rb:75 0.000