Project Number Date
test_Tails_ISO_stable 4575 18 Dec 2023, 18:05

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 17:28.763 Passed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
1:38.683
Before features/support/hooks.rb:245 0.006
Given a computer 0.218
And I create a 7200 MiB disk named "old" 0.058
And I plug USB drive "old" 1.055
And I write an old version of the Tails USB image to disk "old" 22.243
When I start Tails from USB drive "old" with network unplugged 1:10.997
Then the boot device has safe access rights 3.206
And Tails is running from USB drive "old" 0.329
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.065
And udev-watchdog is monitoring the correct device 0.245
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:291 3.557
After features/support/hooks.rb:75 0.007
Tags: @product
2:0.990
Before features/support/hooks.rb:245 0.004
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:6.488
Then Tails is running from USB drive "old" 0.431
And I create a persistent partition 44.526
And I take note of which tps features are available 1.422
Then a Tails persistence partition exists on USB drive "old" 0.891
And I shutdown Tails and wait for the computer to power off 7.047
After features/support/hooks.rb:291 0.153
After features/support/hooks.rb:75 0.009
Tags: @product
2:17.423
Before features/support/hooks.rb:245 0.005
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.873
Then Tails is running from USB drive "old" 0.341
And all tps features are active 2.172
When I write some files expected to persist 1.940
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.242
And all persistence configuration files have safe access rights 0.648
And all persistent directories from the old Tails version have safe access rights 2.793
And I take note of which tps features are available 0.587
And I shutdown Tails and wait for the computer to power off 3.072
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.553
After features/support/hooks.rb:291 0.113
After features/support/hooks.rb:75 0.010
Tags: @product
2:38.482
Before features/support/hooks.rb:245 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.369
And I log in to a new session 16.173
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.080
And I plug USB drive "to_upgrade" 2.454
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:52.873
Then the running Tails is installed on USB drive "to_upgrade" 13.081
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:291 7.075
After features/support/hooks.rb:75 0.000
Tags: @product
1:56.229
Before features/support/hooks.rb:245 0.009
Given a computer 0.273
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:45.972
Then all tps features from the old Tails version are active 1.762
And Tails is running from USB drive "to_upgrade" 0.296
And the boot device has safe access rights 3.541
And the expected persistent files created with the old Tails version are present in the filesystem 1.523
And all persistent directories from the old Tails version have safe access rights 2.860
After features/support/hooks.rb:291 0.863
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:26.276
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 11.478
And no SquashFS delta is installed 0.297
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.323
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.071
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.416
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.585
When the network is plugged 0.050
And Tor is ready 18.840
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 4.094
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 8.849
Given I shutdown Tails and wait for the computer to power off 6.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.300
Then Tails is running version 2.2~testoverlayfsng 0.137
And all tps features are active 2.579
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.485
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.084
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.342
# 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.291
When the network is plugged 0.046
And Tor is ready 44.638
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 0.555
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 9.145
Given I shutdown Tails and wait for the computer to power off 4.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:51.847
Then Tails is running version 2.3~testoverlayfsng 0.103
And all tps features are active 2.612
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.076
# 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.322
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.304
When the network is plugged 0.043
And Tor is ready 15.175
Then the Upgrader considers the system as up-to-date 0.268
# 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 30.461
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.221
After features/support/hooks.rb:291 0.835
After features/support/hooks.rb:75 0.041
Tags: @product @automatic_upgrade
30.676
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 10.039
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.569
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.076
And the signing key used by the Upgrader is outdated 1.985
But a current signing key is available on our website 0.000
When the network is plugged 0.044
And Tor is ready 16.360
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.601
After features/support/hooks.rb:291 0.800
After features/support/hooks.rb:75 0.000