Project Number Date
test_Tails_ISO_stable 4598 01 Jan 2024, 12:30

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:52.810 Passed
6:22.595
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 11.722
And no SquashFS delta is installed 0.109
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.262
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.063
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.393
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.718
When the network is plugged 0.057
And Tor is ready 16.611
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.709
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.350
Given I shutdown Tails and wait for the computer to power off 6.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.755
Then Tails is running version 2.2~testoverlayfsng 0.148
And all tps features are active 2.214
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.365
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.078
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.286
# 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.269
When the network is plugged 0.139
And Tor is ready 15.258
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.687
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.585
Given I shutdown Tails and wait for the computer to power off 4.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.469
Then Tails is running version 2.3~testoverlayfsng 0.112
And all tps features are active 2.206
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.680
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.069
# 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.320
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.460
When the network is plugged 0.045
And Tor is ready 44.214
Then the Upgrader considers the system as up-to-date 0.319
# 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.611
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.537
After features/support/hooks.rb:291 0.760
After features/support/hooks.rb:75 0.023
30.214
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.425
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.298
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.080
And the signing key used by the Upgrader is outdated 1.102
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 17.562
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.698
After features/support/hooks.rb:291 0.784
After features/support/hooks.rb:75 0.000