Project Number Date
test_Tails_ISO_stable 4883 11 Jun 2024, 17:58

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 20:40.196 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:55.862
Before features/support/hooks.rb:269 0.007
Given a computer 0.268
And I create a 7200 MiB disk named "old" 0.080
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 1:15.965
When I start Tails from USB drive "old" with network unplugged 1:34.059
Then the boot device has safe access rights 3.374
And Tails is running from USB drive "old" 0.403
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.092
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:315 7.583
After features/support/hooks.rb:100 0.015
Tags: @product
2:19.908
Before features/support/hooks.rb:269 0.011
Given a computer 0.439
And I start Tails from USB drive "old" with network unplugged and I login 1:24.479
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 37.842
And I take note of which tps features are available 3.727
Then a Tails persistence partition exists on USB drive "old" 1.706
And I shutdown Tails and wait for the computer to power off 11.314
After features/support/hooks.rb:315 0.160
After features/support/hooks.rb:100 0.012
Tags: @product
3:2.230
Before features/support/hooks.rb:269 0.008
Given a computer 1.815
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:21.620
Then Tails is running from USB drive "old" 0.437
And all tps features are active 2.483
When I write some files expected to persist 1.709
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.446
And all persistent directories from the old Tails version have safe access rights 3.145
And I take note of which tps features are available 0.665
And I shutdown Tails and wait for the computer to power off 4.738
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.932
After features/support/hooks.rb:315 0.115
After features/support/hooks.rb:100 0.011
Tags: @product
2:28.088
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.411
And I log in to a new session 19.601
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.579
And I plug USB drive "to_upgrade" 2.508
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.465
Then the running Tails is installed on USB drive "to_upgrade" 19.078
And I unplug USB drive "to_upgrade" 0.247
And I unplug USB drive "__internal" 0.196
After features/support/hooks.rb:315 1.850
After features/support/hooks.rb:100 0.000
Tags: @product
2:15.137
Before features/support/hooks.rb:269 0.007
Given a computer 0.378
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:5.841
Then all tps features from the old Tails version are active 1.559
And Tails is running from USB drive "to_upgrade" 0.342
And the boot device has safe access rights 3.033
And the expected persistent files created with the old Tails version are present in the filesystem 1.470
And all persistent directories from the old Tails version have safe access rights 2.512
After features/support/hooks.rb:315 0.731
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
6:49.192
Before features/support/hooks.rb:269 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.749
And no SquashFS delta is installed 0.093
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.371
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.394
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.462
When the network is plugged 0.041
And Tor is ready 47.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.583
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.728
Given I shutdown Tails and wait for the computer to power off 8.884
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.184
Then Tails is running version 6.2~testoverlayfs 0.016
And all tps features are active 2.438
And the file system changes introduced in version 6.2~testoverlayfs are present 0.320
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.370
# 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.307
When the network is plugged 0.041
And Tor is ready 16.281
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.156
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.876
Given I shutdown Tails and wait for the computer to power off 4.117
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:5.363
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.834
And the file system changes introduced in version 6.3~testoverlayfs are present 0.567
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.356
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.354
When the network is plugged 0.056
And Tor is ready 19.428
Then the Upgrader considers the system as up-to-date 0.326
# 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 15.354
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.904
After features/support/hooks.rb:315 0.754
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
49.777
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 22.954
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.480
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 1.207
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 19.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.193
After features/support/hooks.rb:315 0.736
After features/support/hooks.rb:100 0.000