Project Number Date
test_Tails_ISO_stable 4775 05 Apr 2024, 17:29

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 17:53.278 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:44.492
Before features/support/hooks.rb:259 0.008
Given a computer 0.494
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 23.314
When I start Tails from USB drive "old" with network unplugged 1:15.413
Then the boot device has safe access rights 3.139
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.304
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:305 3.769
After features/support/hooks.rb:89 0.014
Tags: @product
2:6.695
Before features/support/hooks.rb:259 0.009
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:18.408
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 36.541
And I take note of which tps features are available 1.367
Then a Tails persistence partition exists on USB drive "old" 0.779
And I shutdown Tails and wait for the computer to power off 9.000
After features/support/hooks.rb:305 0.159
After features/support/hooks.rb:89 0.010
Tags: @product
2:34.296
Before features/support/hooks.rb:259 0.006
Given a computer 0.212
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:5.605
Then Tails is running from USB drive "old" 0.542
And all tps features are active 1.905
When I write some files expected to persist 1.997
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.261
And all persistence configuration files have safe access rights 0.500
And all persistent directories from the old Tails version have safe access rights 2.539
And I take note of which tps features are available 0.492
And I shutdown Tails and wait for the computer to power off 4.347
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 15.891
After features/support/hooks.rb:305 0.105
After features/support/hooks.rb:89 0.010
Tags: @product
2:24.502
Before features/support/hooks.rb:259 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 11.428
And I log in to a new session 17.123
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.615
And I plug USB drive "to_upgrade" 2.397
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.476
Then the running Tails is installed on USB drive "to_upgrade" 14.956
And I unplug USB drive "to_upgrade" 0.272
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:305 2.502
After features/support/hooks.rb:89 0.000
Tags: @product
2:7.671
Before features/support/hooks.rb:259 0.007
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:58.507
Then all tps features from the old Tails version are active 1.558
And Tails is running from USB drive "to_upgrade" 0.290
And the boot device has safe access rights 3.121
And the expected persistent files created with the old Tails version are present in the filesystem 1.585
And all persistent directories from the old Tails version have safe access rights 2.406
After features/support/hooks.rb:305 0.690
After features/support/hooks.rb:89 0.009
Tags: @product @automatic_upgrade
6:19.193
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.013
And no SquashFS delta is installed 0.129
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.044
And Tor is ready 17.623
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.314
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.257
Given I shutdown Tails and wait for the computer to power off 11.573
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.966
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.436
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
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.353
# 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.290
When the network is plugged 0.040
And Tor is ready 18.732
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.143
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.331
Given I shutdown Tails and wait for the computer to power off 4.348
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.030
Then Tails is running version 6.3~testoverlayfs 0.037
And all tps features are active 2.037
And the file system changes introduced in version 6.3~testoverlayfs are present 0.468
And only the 6.3~testoverlayfs SquashFS delta is installed 0.083
# 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.298
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.287
When the network is plugged 0.047
And Tor is ready 18.447
Then the Upgrader considers the system as up-to-date 10.640
# 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.819
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.878
After features/support/hooks.rb:305 0.722
After features/support/hooks.rb:89 0.021
Tags: @product @automatic_upgrade
36.426
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.784
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.355
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.478
But a current signing key is available on our website 0.000
When the network is plugged 0.042
And Tor is ready 18.772
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.931
After features/support/hooks.rb:305 0.710
After features/support/hooks.rb:89 0.000