Project Number Date
test_Tails_ISO_stable 4642 28 Jan 2024, 12:17

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 7:2.484 Passed
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
6:8.847
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 10.179
And no SquashFS delta is installed 0.075
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.088
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.531
When the network is plugged 0.031
And Tor is ready 15.925
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.591
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.796
Given I shutdown Tails and wait for the computer to power off 6.318
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.913
Then Tails is running version 2.2~testoverlayfsng 0.090
And all tps features are active 1.846
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.398
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.257
# 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.281
When the network is plugged 0.030
And Tor is ready 17.640
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 2.523
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.225
Given I shutdown Tails and wait for the computer to power off 4.091
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.191
Then Tails is running version 2.3~testoverlayfsng 0.096
And all tps features are active 1.739
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.579
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.072
# 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.266
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.497
When the network is plugged 0.029
And Tor is ready 42.906
Then the Upgrader considers the system as up-to-date 0.279
# 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.406
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.232
After features/support/hooks.rb:291 0.790
After features/support/hooks.rb:75 0.015
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
53.636
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 9.777
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.060
And the signing key used by the Upgrader is outdated 0.639
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 42.276
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.570
After features/support/hooks.rb:291 0.888
After features/support/hooks.rb:75 0.000