Project Number Date
test_Tails_ISO_stable 4649 01 Feb 2024, 12:19

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:27.353 Passed
6:0.155
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 12.191
And no SquashFS delta is installed 0.106
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.478
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.086
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.370
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.579
When the network is plugged 0.033
And Tor is ready 17.066
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.655
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.451
Given I shutdown Tails and wait for the computer to power off 6.263
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.079
Then Tails is running version 2.2~testoverlayfsng 0.114
And all tps features are active 2.350
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.375
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.091
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.274
# 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.307
When the network is plugged 0.048
And Tor is ready 15.244
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.820
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.481
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.373
Then Tails is running version 2.3~testoverlayfsng 0.154
And all tps features are active 2.223
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.613
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.088
# 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.330
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.327
When the network is plugged 0.045
And Tor is ready 15.708
Then the Upgrader considers the system as up-to-date 0.271
# 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 29.691
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.578
After features/support/hooks.rb:291 0.854
After features/support/hooks.rb:75 0.021
27.198
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.510
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.329
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.191
And the signing key used by the Upgrader is outdated 0.618
But a current signing key is available on our website 0.000
When the network is plugged 0.046
And Tor is ready 13.477
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.024
After features/support/hooks.rb:291 0.746
After features/support/hooks.rb:75 0.000