Project Number Date
test_Tails_ISO_stable 4976 27 Jul 2024, 18:03

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:38.957 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:3.278
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.225
When I start Tails from USB drive "old" with network unplugged 1:26.507
Then the boot device has safe access rights 3.207
And Tails is running from USB drive "old" 0.340
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.109
And udev-watchdog is monitoring the correct device 0.331
And I unplug USB drive "old" 0.189
After features/support/hooks.rb:326 9.963
After features/support/hooks.rb:100 0.010
Tags: @product
2:10.330
Before features/support/hooks.rb:269 0.008
Given a computer 0.243
And I start Tails from USB drive "old" with network unplugged and I login 1:26.791
Then Tails is running from USB drive "old" 0.319
And I create a persistent partition 32.306
And I take note of which tps features are available 1.623
Then a Tails persistence partition exists on USB drive "old" 0.848
And I shutdown Tails and wait for the computer to power off 8.196
After features/support/hooks.rb:326 0.216
After features/support/hooks.rb:100 0.010
Tags: @product
2:48.444
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:11.616
Then Tails is running from USB drive "old" 0.375
And all tps features are active 2.144
When I write some files expected to persist 1.639
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.377
And all persistent directories from the old Tails version have safe access rights 2.328
And I take note of which tps features are available 0.563
And I shutdown Tails and wait for the computer to power off 4.340
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.649
After features/support/hooks.rb:326 0.156
After features/support/hooks.rb:100 0.011
Tags: @product
2:24.909
Before features/support/hooks.rb:269 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.420
And I log in to a new session 18.101
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.451
And I plug USB drive "to_upgrade" 2.371
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.418
Then the running Tails is installed on USB drive "to_upgrade" 16.698
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.242
After features/support/hooks.rb:326 8.134
After features/support/hooks.rb:100 0.000
Tags: @product
2:17.134
Before features/support/hooks.rb:269 0.009
Given a computer 0.225
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:7.603
Then all tps features from the old Tails version are active 1.660
And Tails is running from USB drive "to_upgrade" 0.353
And the boot device has safe access rights 3.425
And the expected persistent files created with the old Tails version are present in the filesystem 1.426
And all persistent directories from the old Tails version have safe access rights 2.440
After features/support/hooks.rb:326 0.663
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:20.023
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 14.159
And no SquashFS delta is installed 0.159
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.362
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.309
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.519
When the network is plugged 0.122
And Tor is ready 18.937
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.858
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.601
Given I shutdown Tails and wait for the computer to power off 11.245
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:1.623
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 2.311
And the file system changes introduced in version 6.2~testoverlayfs are present 0.315
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.362
# 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.348
When the network is plugged 0.045
And Tor is ready 18.501
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.229
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.547
Given I shutdown Tails and wait for the computer to power off 4.378
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.681
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.122
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.369
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.292
When the network is plugged 0.047
And Tor is ready 18.919
Then the Upgrader considers the system as up-to-date 0.329
# 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.555
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.069
After features/support/hooks.rb:326 0.812
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
34.836
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 10.648
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.376
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.808
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 17.771
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.133
After features/support/hooks.rb:326 0.595
After features/support/hooks.rb:100 0.000