Project Number Date
test_Tails_ISO_stable 5570 12 Apr 2025, 12:55

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 19:37.951 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:0.692
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.053
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 30.002
When I start Tails from USB drive "old" with network unplugged 1:25.519
Then the boot device has safe access rights 2.878
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.087
And process "udev-watchdog" is running 0.087
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.194
After features/support/hooks.rb:330 3.513
After features/support/hooks.rb:100 0.084
Tags: @product
2:7.990
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.220
And I start Tails from USB drive "old" with network unplugged and I login 1:25.945
Then Tails is running from USB drive "old" 0.399
And I create a persistent partition 32.276
And I take note of which tps features are available 1.673
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 6.732
After features/support/hooks.rb:330 0.186
After features/support/hooks.rb:100 0.009
Tags: @product
2:55.281
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.213
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.778
Then Tails is running from USB drive "old" 0.400
And all tps features are active 2.114
When I write some files expected to persist 2.267
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.222
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.742
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 4.496
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.170
After features/support/hooks.rb:330 0.122
After features/support/hooks.rb:100 0.008
Tags: @product
2:34.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.323
And I log in to a new session 22.056
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.582
And I plug USB drive "to_upgrade" 2.463
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.833
Then the running Tails is installed on USB drive "to_upgrade" 22.180
And I unplug USB drive "to_upgrade" 0.197
And I unplug USB drive "__internal" 0.204
After features/support/hooks.rb:330 3.169
After features/support/hooks.rb:100 0.000
Tags: @product
2:19.542
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.175
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:9.505
Then all tps features from the old Tails version are active 2.009
And Tails is running from USB drive "to_upgrade" 0.329
And the boot device has safe access rights 3.496
And the expected persistent files created with the old Tails version are present in the filesystem 1.409
And all persistent directories from the old Tails version have safe access rights 2.616
After features/support/hooks.rb:330 1.233
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
7:1.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.453
And no SquashFS delta is installed 0.104
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.363
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.264
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.523
When the network is plugged 0.072
And Tor is ready 20.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.556
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.050
Given I shutdown Tails and wait for the computer to power off 8.923
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.479
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 4.353
And the file system changes introduced in version 6.2~testoverlayfs are present 0.384
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.359
# 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.280
When the network is plugged 0.075
And Tor is ready 19.457
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.366
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.806
Given I shutdown Tails and wait for the computer to power off 4.328
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.993
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.138
And the file system changes introduced in version 6.3~testoverlayfs are present 0.528
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.321
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.068
And Tor is ready 46.438
Then the Upgrader considers the system as up-to-date 0.328
# 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 16.814
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.690
After features/support/hooks.rb:330 0.740
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
38.010
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.017
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.079
And Tor is ready 18.662
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.625
After features/support/hooks.rb:330 0.937
After features/support/hooks.rb:100 0.000