Project Number Date
test_Tails_ISO_codespell 14 28 Jun 2025, 11:00

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 26:3.413 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:54.254
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.350
And I create a 7200 MiB disk named "old" 0.067
And I plug USB drive "old" 1.094
And I write an old version of the Tails USB image to disk "old" 45.244
When I start Tails from USB drive "old" with network unplugged 2:2.800
Then the boot device has safe access rights 3.684
And Tails is running from USB drive "old" 0.371
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.090
And udev-watchdog is monitoring the correct device 0.270
And I unplug USB drive "old" 0.208
After features/support/hooks.rb:330 7.174
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.698
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.268
And I start Tails from USB drive "old" with network unplugged and I login 1:52.105
Then Tails is running from USB drive "old" 0.376
And I create a persistent partition 45.264
And I take note of which tps features are available 3.703
Then a Tails persistence partition exists on USB drive "old" 1.292
And I shutdown Tails and wait for the computer to power off 8.687
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.009
Tags: @product
4:3.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:10.530
Then Tails is running from USB drive "old" 0.946
And all tps features are active 2.176
When I write some files expected to persist 1.914
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.244
And all persistence configuration files have safe access rights 0.478
And all persistent directories from the old Tails version have safe access rights 3.268
And I take note of which tps features are available 0.474
And I shutdown Tails and wait for the computer to power off 8.716
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 34.275
After features/support/hooks.rb:330 1.529
After features/support/hooks.rb:100 0.015
Tags: @product
3:12.983
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 without a persistent partition and stopped at Tails Greeter's login screen 12.513
And I log in to a new session 29.748
And I clone USB drive "old" to a new USB drive "to_upgrade" 5.617
And I plug USB drive "to_upgrade" 2.585
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:51.923
Then the running Tails is installed on USB drive "to_upgrade" 29.735
And I unplug USB drive "to_upgrade" 0.215
And I unplug USB drive "__internal" 0.644
After features/support/hooks.rb:330 3.074
After features/support/hooks.rb:100 0.000
Tags: @product
3:16.155
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.223
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:59.936
Then all tps features from the old Tails version are active 5.286
And Tails is running from USB drive "to_upgrade" 0.584
And the boot device has safe access rights 5.379
And the expected persistent files created with the old Tails version are present in the filesystem 1.626
And all persistent directories from the old Tails version have safe access rights 3.117
After features/support/hooks.rb:330 2.342
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
8:54.620
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 18.473
And no SquashFS delta is installed 0.229
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.523
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.486
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.592
When the network is plugged 0.088
And Tor is ready 30.649
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 7.822
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 17.433
Given I shutdown Tails and wait for the computer to power off 15.897
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:49.376
Then Tails is running version 6.2~testoverlayfs 0.109
And all tps features are active 5.793
And the file system changes introduced in version 6.2~testoverlayfs are present 0.501
And only the 6.2~testoverlayfs SquashFS delta is installed 0.259
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.822
# 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.446
When the network is plugged 0.167
And Tor is ready 21.405
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 8.039
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.518
Given I shutdown Tails and wait for the computer to power off 4.975
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:41.331
Then Tails is running version 6.3~testoverlayfs 0.018
And all tps features are active 6.378
And the file system changes introduced in version 6.3~testoverlayfs are present 1.309
And only the 6.3~testoverlayfs SquashFS delta is installed 0.164
# 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.496
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.377
When the network is plugged 0.079
And Tor is ready 22.541
Then the Upgrader considers the system as up-to-date 0.302
# 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.250
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.658
After features/support/hooks.rb:330 0.671
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
50.487
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.321
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.473
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.090
And the signing key used by the Upgrader is outdated 0.126
But a current signing key is available on our website 0.000
When the network is plugged 0.121
And Tor is ready 23.875
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 13.478
After features/support/hooks.rb:330 1.624
After features/support/hooks.rb:100 0.000