Project Number Date
test_Tails_ISO_stable 4636 25 Jan 2024, 15: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:19.109 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:25.358
Before features/support/hooks.rb:245 0.006
Given a computer 0.245
And I create a 7200 MiB disk named "old" 0.095
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 17.400
When I start Tails from USB drive "old" with network unplugged 1:2.348
Then the boot device has safe access rights 3.280
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.247
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:291 3.475
After features/support/hooks.rb:75 0.013
Tags: @product
1:56.582
Before features/support/hooks.rb:245 0.007
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:3.721
Then Tails is running from USB drive "old" 0.381
And I create a persistent partition 42.937
And I take note of which tps features are available 1.392
Then a Tails persistence partition exists on USB drive "old" 0.924
And I shutdown Tails and wait for the computer to power off 7.057
After features/support/hooks.rb:291 0.115
After features/support/hooks.rb:75 0.011
Tags: @product
2:19.658
Before features/support/hooks.rb:245 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:51.841
Then Tails is running from USB drive "old" 0.401
And all tps features are active 2.373
When I write some files expected to persist 1.887
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.294
And all persistence configuration files have safe access rights 0.422
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.459
And I shutdown Tails and wait for the computer to power off 4.159
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.051
After features/support/hooks.rb:291 0.134
After features/support/hooks.rb:75 0.009
Tags: @product
2:32.195
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 9.376
And I log in to a new session 17.879
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.078
And I plug USB drive "to_upgrade" 2.460
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.031
Then the running Tails is installed on USB drive "to_upgrade" 13.987
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:291 1.089
After features/support/hooks.rb:75 0.000
Tags: @product
1:58.833
Before features/support/hooks.rb:245 0.006
Given a computer 0.149
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:48.694
Then all tps features from the old Tails version are active 1.571
And Tails is running from USB drive "to_upgrade" 0.344
And the boot device has safe access rights 3.674
And the expected persistent files created with the old Tails version are present in the filesystem 1.555
And all persistent directories from the old Tails version have safe access rights 2.842
After features/support/hooks.rb:291 1.011
After features/support/hooks.rb:75 0.010
Tags: @product @automatic_upgrade
6:35.960
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 14.386
And no SquashFS delta is installed 0.313
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.379
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.059
And the file system changes introduced in version 2.2~testoverlayfsng are not present 0.531
And the file system changes introduced in version 2.3~testoverlayfsng are not present 0.550
When the network is plugged 0.038
And Tor is ready 44.437
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 0.611
And I can successfully install the incremental upgrade to version 2.2~testoverlayfsng 9.137
Given I shutdown Tails and wait for the computer to power off 6.080
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.114
Then Tails is running version 2.2~testoverlayfsng 0.135
And all tps features are active 2.498
And the file system changes introduced in version 2.2~testoverlayfsng are present 0.363
And only the 2.2~testoverlayfsng SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.269
# 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.380
When the network is plugged 0.050
And Tor is ready 14.597
Then I am proposed to install an incremental upgrade to version 2.3~testoverlayfsng 1.602
And I can successfully install the incremental upgrade to version 2.3~testoverlayfsng 10.403
Given I shutdown Tails and wait for the computer to power off 4.686
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:48.331
Then Tails is running version 2.3~testoverlayfsng 0.140
And all tps features are active 2.101
And the file system changes introduced in version 2.3~testoverlayfsng are present 0.691
And only the 2.3~testoverlayfsng SquashFS delta is installed 0.070
# 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.307
And Tails is fooled to think that version 2.1~testoverlayfsng was initially installed 0.338
When the network is plugged 0.038
And Tor is ready 15.988
Then the Upgrader considers the system as up-to-date 0.314
# 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 26.623
And the file system changes introduced in version 2.3~testoverlayfsng are present in the Unsafe Browser's chroot 1.336
After features/support/hooks.rb:291 0.773
After features/support/hooks.rb:75 0.017
Tags: @product @automatic_upgrade
30.520
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 9.606
And Tails is fooled to think that version 2.0~testoverlayfsng was initially installed 0.428
And Tails is fooled to think it is running version 2.0~testoverlayfsng 0.102
And the signing key used by the Upgrader is outdated 0.506
But a current signing key is available on our website 0.000
When the network is plugged 0.127
And Tor is ready 17.849
Then I am proposed to install an incremental upgrade to version 2.2~testoverlayfsng 1.900
After features/support/hooks.rb:291 0.761
After features/support/hooks.rb:75 0.000