Project Number Date
test_Tails_ISO_stable 4874 05 Jun 2024, 12:31

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 19:16.600 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:6.924
Before features/support/hooks.rb:269 0.005
Given a computer 0.184
And I create a 7200 MiB disk named "old" 0.038
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.435
When I start Tails from USB drive "old" with network unplugged 1:31.245
Then the boot device has safe access rights 2.999
And Tails is running from USB drive "old" 0.322
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.172
After features/support/hooks.rb:315 3.799
After features/support/hooks.rb:100 0.010
Tags: @product
2:11.412
Before features/support/hooks.rb:269 0.007
Given a computer 0.201
And I start Tails from USB drive "old" with network unplugged and I login 1:24.403
Then Tails is running from USB drive "old" 0.361
And I create a persistent partition 35.658
And I take note of which tps features are available 1.427
Then a Tails persistence partition exists on USB drive "old" 0.844
And I shutdown Tails and wait for the computer to power off 8.514
After features/support/hooks.rb:315 0.185
After features/support/hooks.rb:100 0.008
Tags: @product
2:49.455
Before features/support/hooks.rb:269 0.005
Given a computer 0.303
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.689
Then Tails is running from USB drive "old" 0.439
And all tps features are active 2.226
When I write some files expected to persist 1.729
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.931
And I take note of which tps features are available 0.407
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.818
After features/support/hooks.rb:315 0.136
After features/support/hooks.rb:100 0.010
Tags: @product
2:29.034
Before features/support/hooks.rb:269 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 11.652
And I log in to a new session 19.356
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.809
And I plug USB drive "to_upgrade" 2.487
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.586
Then the running Tails is installed on USB drive "to_upgrade" 19.717
And I unplug USB drive "to_upgrade" 0.221
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:315 4.389
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.598
Before features/support/hooks.rb:269 0.005
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:8.114
Then all tps features from the old Tails version are active 1.583
And Tails is running from USB drive "to_upgrade" 0.339
And the boot device has safe access rights 3.024
And the expected persistent files created with the old Tails version are present in the filesystem 1.787
And all persistent directories from the old Tails version have safe access rights 2.558
After features/support/hooks.rb:315 0.963
After features/support/hooks.rb:100 0.031
Tags: @product @automatic_upgrade
6:46.194
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 12.401
And no SquashFS delta is installed 0.165
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.316
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.366
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.536
When the network is plugged 0.070
And Tor is ready 20.127
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.290
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.974
Given I shutdown Tails and wait for the computer to power off 8.800
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.532
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.018
And the file system changes introduced in version 6.2~testoverlayfs are present 0.340
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.354
# 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.311
When the network is plugged 0.042
And Tor is ready 28.418
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.811
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.290
Given I shutdown Tails and wait for the computer to power off 4.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:3.842
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 1.926
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.359
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.054
And Tor is ready 16.536
Then the Upgrader considers the system as up-to-date 10.737
# 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.338
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.766
After features/support/hooks.rb:315 0.680
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
35.980
Before features/support/hooks.rb:269 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.886
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.570
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 1.369
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 17.648
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.420
After features/support/hooks.rb:315 0.800
After features/support/hooks.rb:100 0.000