Project Number Date
test_Tails_ISO_stable 4663 13 Feb 2024, 17:32

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:57.615 Passed
6:29.803
Before features/support/hooks.rb:245 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.039
And no SquashFS delta is installed 0.168
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.322
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.040
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.450
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.641
When the network is plugged 0.021
And Tor is ready 45.024
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.572
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 7.498
Given I shutdown Tails and wait for the computer to power off 5.063
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:54.125
Then Tails is running version 2.2~testoverlayfsng 0.173
And all tps features are active 2.045
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.530
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.099
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.340
# 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.438
When the network is plugged 0.034
And Tor is ready 16.859
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 3.167
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 8.538
Given I shutdown Tails and wait for the computer to power off 4.330
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.927
Then Tails is running version 2.3~testoverlayfsng 0.169
And all tps features are active 2.046
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.779
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.106
# 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.368
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.373
When the network is plugged 0.044
And Tor is ready 19.129
Then the Upgrader considers the system as up-to-date 0.292
# 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 28.624
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.416
After features/support/hooks.rb:291 0.810
After features/support/hooks.rb:75 0.019
27.811
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.543
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.357
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.055
And the signing key used by the Upgrader is outdated 0.650
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 13.502
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 3.654
After features/support/hooks.rb:291 0.752
After features/support/hooks.rb:75 0.000