Project Number Date
test_Tails_ISO_stable 4625 19 Jan 2024, 13:33

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:34.226 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.780
Before features/support/hooks.rb:245 0.005
Given a computer 0.222
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.075
And I write an old version of the Tails USB image to disk "old" 22.494
When I start Tails from USB drive "old" with network unplugged 1:10.592
Then the boot device has safe access rights 3.323
And Tails is running from USB drive "old" 0.369
And there is no persistence partition on USB drive "old" 0.075
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.309
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:291 3.745
After features/support/hooks.rb:75 0.009
Tags: @product
1:57.189
Before features/support/hooks.rb:245 0.006
Given a computer 0.246
And I start Tails from USB drive "old" with network unplugged and I login 1:3.211
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 43.954
And I take note of which tps features are available 1.285
Then a Tails persistence partition exists on USB drive "old" 1.000
And I shutdown Tails and wait for the computer to power off 7.104
After features/support/hooks.rb:291 0.121
After features/support/hooks.rb:75 0.009
Tags: @product
2:24.203
Before features/support/hooks.rb:245 0.004
Given a computer 0.203
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:55.006
Then Tails is running from USB drive "old" 0.434
And all tps features are active 2.300
When I write some files expected to persist 2.017
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.239
And all persistence configuration files have safe access rights 0.666
And all persistent directories from the old Tails version have safe access rights 2.998
And I take note of which tps features are available 0.463
And I shutdown Tails and wait for the computer to power off 3.281
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 16.592
After features/support/hooks.rb:291 0.140
After features/support/hooks.rb:75 0.010
Tags: @product
2:32.382
Before features/support/hooks.rb:245 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.082
And I log in to a new session 17.321
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.295
And I plug USB drive "to_upgrade" 2.448
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:48.430
Then the running Tails is installed on USB drive "to_upgrade" 12.415
And I unplug USB drive "to_upgrade" 0.218
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:291 1.729
After features/support/hooks.rb:75 0.000
Tags: @product
2:2.803
Before features/support/hooks.rb:245 0.005
Given a computer 0.200
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:51.702
Then all tps features from the old Tails version are active 1.741
And Tails is running from USB drive "to_upgrade" 0.351
And the boot device has safe access rights 3.735
And the expected persistent files created with the old Tails version are present in the filesystem 1.875
And all persistent directories from the old Tails version have safe access rights 3.196
After features/support/hooks.rb:291 1.043
After features/support/hooks.rb:75 0.024
Tags: @product @automatic_upgrade
6:31.070
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 15.096
And no SquashFS delta is installed 0.150
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.430
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.062
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.349
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.698
When the network is plugged 0.038
And Tor is ready 45.390
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.610
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.054
Given I shutdown Tails and wait for the computer to power off 10.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.876
Then Tails is running version 2.2~testoverlayfsng 0.107
And all tps features are active 2.636
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.535
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.325
# 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.325
When the network is plugged 0.607
And Tor is ready 16.754
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.701
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 7.891
Given I shutdown Tails and wait for the computer to power off 4.085
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.643
Then Tails is running version 2.3~testoverlayfsng 0.128
And all tps features are active 2.405
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.720
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.090
# 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.326
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.483
When the network is plugged 0.041
And Tor is ready 16.941
Then the Upgrader considers the system as up-to-date 0.267
# 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 25.347
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.620
After features/support/hooks.rb:291 0.836
After features/support/hooks.rb:75 0.021
Tags: @product @automatic_upgrade
27.795
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 9.505
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.302
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.069
And the signing key used by the Upgrader is outdated 0.581
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 14.374
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 2.929
After features/support/hooks.rb:291 0.741
After features/support/hooks.rb:75 0.000