Project Number Date
test_Tails_ISO_stable 5050 27 Aug 2024, 12:16

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:45.137 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:11.314
Before features/support/hooks.rb:269 0.006
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.040
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 31.279
When I start Tails from USB drive "old" with network unplugged 1:34.670
Then the boot device has safe access rights 3.109
And Tails is running from USB drive "old" 0.305
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.324
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:326 7.054
After features/support/hooks.rb:100 0.008
Tags: @product
2:1.269
Before features/support/hooks.rb:269 0.005
Given a computer 0.188
And I start Tails from USB drive "old" with network unplugged and I login 1:19.871
Then Tails is running from USB drive "old" 0.369
And I create a persistent partition 30.277
And I take note of which tps features are available 1.297
Then a Tails persistence partition exists on USB drive "old" 0.793
And I shutdown Tails and wait for the computer to power off 8.471
After features/support/hooks.rb:326 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
2:52.400
Before features/support/hooks.rb:269 0.007
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.886
Then Tails is running from USB drive "old" 0.334
And all tps features are active 2.012
When I write some files expected to persist 1.810
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.482
And I take note of which tps features are available 0.447
And I shutdown Tails and wait for the computer to power off 4.292
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.369
After features/support/hooks.rb:326 0.135
After features/support/hooks.rb:100 0.010
Tags: @product
2:23.963
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.508
And I log in to a new session 17.702
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.732
And I plug USB drive "to_upgrade" 2.417
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.827
Then the running Tails is installed on USB drive "to_upgrade" 19.375
And I unplug USB drive "to_upgrade" 0.198
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:326 7.306
After features/support/hooks.rb:100 0.000
Tags: @product
2:25.934
Before features/support/hooks.rb:269 0.007
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.448
Then all tps features from the old Tails version are active 1.525
And Tails is running from USB drive "to_upgrade" 0.394
And the boot device has safe access rights 3.409
And the expected persistent files created with the old Tails version are present in the filesystem 1.512
And all persistent directories from the old Tails version have safe access rights 2.468
After features/support/hooks.rb:326 1.006
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
6:15.568
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 11.578
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
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.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.459
When the network is plugged 0.071
And Tor is ready 20.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.494
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 9.834
Given I shutdown Tails and wait for the computer to power off 10.801
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.024
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.126
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.315
# 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.272
When the network is plugged 0.072
And Tor is ready 19.307
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.074
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.219
Given I shutdown Tails and wait for the computer to power off 4.313
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:2.029
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.071
And the file system changes introduced in version 6.3~testoverlayfs are present 0.494
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.305
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.333
When the network is plugged 0.067
And Tor is ready 18.748
Then the Upgrader considers the system as up-to-date 0.306
# 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 13.514
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.902
After features/support/hooks.rb:326 0.775
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
34.687
Before features/support/hooks.rb:269 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.441
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.711
But a current signing key is available on our website 0.000
When the network is plugged 0.072
And Tor is ready 18.981
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.120
After features/support/hooks.rb:326 0.618
After features/support/hooks.rb:100 0.000