Project Number Date
test_Tails_ISO_stable 4687 29 Feb 2024, 15:02

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:13.118 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:29.463
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 19.607
When I start Tails from USB drive "old" with network unplugged 1:4.684
Then the boot device has safe access rights 2.823
And Tails is running from USB drive "old" 0.376
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.267
After features/support/hooks.rb:291 7.491
After features/support/hooks.rb:75 0.010
Tags: @product
2:7.517
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login 1:15.843
Then Tails is running from USB drive "old" 0.353
And I create a persistent partition 40.304
And I take note of which tps features are available 1.848
Then a Tails persistence partition exists on USB drive "old" 0.808
And I shutdown Tails and wait for the computer to power off 8.174
After features/support/hooks.rb:291 0.188
After features/support/hooks.rb:75 0.009
Tags: @product
2:37.643
Before features/support/hooks.rb:245 0.006
Given a computer 0.183
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:10.783
Then Tails is running from USB drive "old" 0.341
And all tps features are active 1.985
When I write some files expected to persist 1.766
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.300
And all persistence configuration files have safe access rights 0.426
And all persistent directories from the old Tails version have safe access rights 2.536
And I take note of which tps features are available 0.499
And I shutdown Tails and wait for the computer to power off 4.018
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.802
After features/support/hooks.rb:291 0.152
After features/support/hooks.rb:75 0.008
Tags: @product
2:31.368
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.634
And I log in to a new session 16.225
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.480
And I plug USB drive "to_upgrade" 2.394
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.512
Then the running Tails is installed on USB drive "to_upgrade" 13.704
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.203
After features/support/hooks.rb:291 1.888
After features/support/hooks.rb:75 0.000
Tags: @product
2:19.710
Before features/support/hooks.rb:245 0.007
Given a computer 0.182
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:10.958
Then all tps features from the old Tails version are active 1.459
And Tails is running from USB drive "to_upgrade" 0.325
And the boot device has safe access rights 2.949
And the expected persistent files created with the old Tails version are present in the filesystem 1.405
And all persistent directories from the old Tails version have safe access rights 2.430
After features/support/hooks.rb:291 0.782
After features/support/hooks.rb:75 0.011
Tags: @product @automatic_upgrade
6:34.187
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 10.724
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.273
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.505
When the network is plugged 0.036
And Tor is ready 19.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.251
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.939
Given I shutdown Tails and wait for the computer to power off 9.032
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.647
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.307
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.299
# 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.243
When the network is plugged 0.040
And Tor is ready 19.687
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.970
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.854
Given I shutdown Tails and wait for the computer to power off 4.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:11.344
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.831
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.089
# 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.292
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.282
When the network is plugged 0.070
And Tor is ready 15.448
Then the Upgrader considers the system as up-to-date 0.211
# 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.038
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.965
After features/support/hooks.rb:291 0.644
After features/support/hooks.rb:75 0.036
Tags: @product @automatic_upgrade
33.228
Before features/support/hooks.rb:245 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.344
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.563
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 16.902
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.265
After features/support/hooks.rb:291 0.638
After features/support/hooks.rb:75 0.000