Project Number Date
test_Tails_ISO_stable 5336 15 Dec 2024, 12:21

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:57.042 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:1.061
Before features/support/hooks.rb:269 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.045
And I plug USB drive "old" 1.052
And I write an old version of the Tails USB image to disk "old" 29.369
When I start Tails from USB drive "old" with network unplugged 1:26.223
Then the boot device has safe access rights 3.144
And Tails is running from USB drive "old" 0.373
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.106
And udev-watchdog is monitoring the correct device 0.299
And I unplug USB drive "old" 0.195
After features/support/hooks.rb:326 3.505
After features/support/hooks.rb:100 0.023
Tags: @product
2:4.430
Before features/support/hooks.rb:269 0.006
Given a computer 0.192
And I start Tails from USB drive "old" with network unplugged and I login 1:23.930
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 30.878
And I take note of which tps features are available 1.907
Then a Tails persistence partition exists on USB drive "old" 0.737
And I shutdown Tails and wait for the computer to power off 6.477
After features/support/hooks.rb:326 0.188
After features/support/hooks.rb:100 0.009
Tags: @product
2:49.304
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:12.027
Then Tails is running from USB drive "old" 0.695
And all tps features are active 1.986
When I write some files expected to persist 1.485
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.387
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 3.245
And I take note of which tps features are available 0.414
And I shutdown Tails and wait for the computer to power off 4.677
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 23.763
After features/support/hooks.rb:326 0.093
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.096
Before features/support/hooks.rb:269 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 10.757
And I log in to a new session 18.383
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.690
And I plug USB drive "to_upgrade" 2.464
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.689
Then the running Tails is installed on USB drive "to_upgrade" 23.674
And I unplug USB drive "to_upgrade" 0.214
And I unplug USB drive "__internal" 0.222
After features/support/hooks.rb:326 2.550
After features/support/hooks.rb:100 0.000
Tags: @product
2:11.229
Before features/support/hooks.rb:269 0.006
Given a computer 0.195
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:1.696
Then all tps features from the old Tails version are active 1.564
And Tails is running from USB drive "to_upgrade" 0.324
And the boot device has safe access rights 3.354
And the expected persistent files created with the old Tails version are present in the filesystem 1.705
And all persistent directories from the old Tails version have safe access rights 2.388
After features/support/hooks.rb:326 0.696
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:43.826
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 12.264
And no SquashFS delta is installed 0.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.814
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.310
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.156
And Tor is ready 22.517
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.381
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.656
Given I shutdown Tails and wait for the computer to power off 10.628
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.546
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.104
And the file system changes introduced in version 6.2~testoverlayfs are present 0.406
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.301
# 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.267
When the network is plugged 0.091
And Tor is ready 18.282
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 6.611
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.180
Given I shutdown Tails and wait for the computer to power off 4.315
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:52.566
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.997
And the file system changes introduced in version 6.3~testoverlayfs are present 0.463
And only the 6.3~testoverlayfs SquashFS delta is installed 0.076
# 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.301
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.302
When the network is plugged 0.065
And Tor is ready 47.229
Then the Upgrader considers the system as up-to-date 0.312
# 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.004
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.898
After features/support/hooks.rb:326 0.750
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
35.095
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 9.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the signing key used by the Upgrader is outdated 0.884
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 17.262
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.706
After features/support/hooks.rb:326 0.689
After features/support/hooks.rb:100 0.000