Project Number Date
test_Tails_ISO_codespell 16 30 Jun 2025, 11:01

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 25:47.933 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:44.916
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.023
Given a computer 0.541
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 41.419
When I start Tails from USB drive "old" with network unplugged 1:57.305
Then the boot device has safe access rights 3.289
And Tails is running from USB drive "old" 0.367
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.095
And udev-watchdog is monitoring the correct device 0.382
And I unplug USB drive "old" 0.339
After features/support/hooks.rb:330 3.771
After features/support/hooks.rb:100 0.008
Tags: @product
3:6.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 2:7.882
Then Tails is running from USB drive "old" 1.297
And I create a persistent partition 42.124
And I take note of which tps features are available 2.165
Then a Tails persistence partition exists on USB drive "old" 0.732
And I shutdown Tails and wait for the computer to power off 11.878
After features/support/hooks.rb:330 0.271
After features/support/hooks.rb:100 0.025
Tags: @product
4:6.989
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.030
Given a computer 0.361
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:10.015
Then Tails is running from USB drive "old" 0.809
And all tps features are active 2.241
When I write some files expected to persist 6.110
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.649
And all persistence configuration files have safe access rights 0.773
And all persistent directories from the old Tails version have safe access rights 4.146
And I take note of which tps features are available 0.471
And I shutdown Tails and wait for the computer to power off 4.303
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 37.106
After features/support/hooks.rb:330 0.159
After features/support/hooks.rb:100 0.012
Tags: @product
3:15.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 13.853
And I log in to a new session 27.084
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.954
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:47.845
Then the running Tails is installed on USB drive "to_upgrade" 41.629
And I unplug USB drive "to_upgrade" 0.330
And I unplug USB drive "__internal" 0.249
After features/support/hooks.rb:330 2.862
After features/support/hooks.rb:100 0.000
Tags: @product
3:4.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.189
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:47.656
Then all tps features from the old Tails version are active 5.022
And Tails is running from USB drive "to_upgrade" 1.488
And the boot device has safe access rights 6.276
And the expected persistent files created with the old Tails version are present in the filesystem 1.499
And all persistent directories from the old Tails version have safe access rights 2.812
After features/support/hooks.rb:330 1.315
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
8:46.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 17.142
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.555
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.613
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.633
When the network is plugged 0.143
And Tor is ready 21.883
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 9.206
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 21.167
Given I shutdown Tails and wait for the computer to power off 11.136
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:50.786
Then Tails is running version 6.2~testoverlayfs 0.018
And all tps features are active 2.420
And the file system changes introduced in version 6.2~testoverlayfs are present 0.302
And only the 6.2~testoverlayfs SquashFS delta is installed 0.082
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.418
# 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.309
When the network is plugged 0.072
And Tor is ready 23.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 10.496
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 17.984
Given I shutdown Tails and wait for the computer to power off 6.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:34.351
Then Tails is running version 6.3~testoverlayfs 0.091
And all tps features are active 2.566
And the file system changes introduced in version 6.3~testoverlayfs are present 0.585
And only the 6.3~testoverlayfs SquashFS delta is installed 0.084
# 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.352
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.361
When the network is plugged 0.079
And Tor is ready 26.332
Then the Upgrader considers the system as up-to-date 0.399
# 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 20.229
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 4.664
After features/support/hooks.rb:330 1.214
After features/support/hooks.rb:100 0.027
Tags: @product @automatic_upgrade
43.171
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 11.771
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.347
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.076
And Tor is ready 22.002
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 8.823
After features/support/hooks.rb:330 1.040
After features/support/hooks.rb:100 0.000