Project Number Date
test_Tails_ISO_devel 3489 22 Aug 2024, 12:34

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 18:37.454 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
2:2.341
Before features/support/hooks.rb:269 0.007
Given a computer 0.215
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 29.382
When I start Tails from USB drive "old" with network unplugged 1:27.524
Then the boot device has safe access rights 3.054
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.116
And udev-watchdog is monitoring the correct device 0.287
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:326 3.921
After features/support/hooks.rb:100 0.011
Tags: @product
2:3.543
Before features/support/hooks.rb:269 0.007
Given a computer 0.311
And I start Tails from USB drive "old" with network unplugged and I login 1:21.260
Then Tails is running from USB drive "old" 0.304
And I create a persistent partition 31.032
And I take note of which tps features are available 1.486
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 8.335
After features/support/hooks.rb:326 0.147
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.057
Before features/support/hooks.rb:269 0.007
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:14.830
Then Tails is running from USB drive "old" 0.378
And all tps features are active 2.154
When I write some files expected to persist 1.793
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.211
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 2.889
And I take note of which tps features are available 0.458
And I shutdown Tails and wait for the computer to power off 4.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.443
After features/support/hooks.rb:326 0.141
After features/support/hooks.rb:100 0.011
Tags: @product
2:27.929
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 10.893
And I log in to a new session 18.572
And I clone USB drive "old" to a new USB drive "to_upgrade" 3.009
And I plug USB drive "to_upgrade" 2.357
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.364
Then the running Tails is installed on USB drive "to_upgrade" 19.314
And I unplug USB drive "to_upgrade" 0.201
And I unplug USB drive "__internal" 0.215
After features/support/hooks.rb:326 2.344
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.845
Before features/support/hooks.rb:269 0.006
Given a computer 0.198
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:2.364
Then all tps features from the old Tails version are active 1.642
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.338
And the expected persistent files created with the old Tails version are present in the filesystem 1.630
And all persistent directories from the old Tails version have safe access rights 2.346
After features/support/hooks.rb:326 0.611
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:22.241
Before features/support/hooks.rb:269 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.380
And no SquashFS delta is installed 0.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.348
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.579
When the network is plugged 0.115
And Tor is ready 18.364
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.475
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.736
Given I shutdown Tails and wait for the computer to power off 8.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:6.313
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.390
And the file system changes introduced in version 6.2~testoverlayfs are present 0.326
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.301
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.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 6.1~testoverlayfs was initially installed 0.270
When the network is plugged 0.076
And Tor is ready 16.170
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.518
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.839
Given I shutdown Tails and wait for the computer to power off 4.387
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.208
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 2.068
And the file system changes introduced in version 6.3~testoverlayfs are present 0.531
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.373
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.077
And Tor is ready 20.182
Then the Upgrader considers the system as up-to-date 0.328
# 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 14.178
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.107
After features/support/hooks.rb:326 0.778
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
37.494
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.947
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.299
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the signing key used by the Upgrader is outdated 0.809
But a current signing key is available on our website 0.000
When the network is plugged 0.126
And Tor is ready 19.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.443
After features/support/hooks.rb:326 0.740
After features/support/hooks.rb:100 0.000