Project Number Date
test_Tails_ISO_codespell 13 27 Jun 2025, 11:15

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 27:15.495 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
3:10.288
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.020
Given a computer 0.358
And I create a 7200 MiB disk named "old" 0.044
And I plug USB drive "old" 1.074
And I write an old version of the Tails USB image to disk "old" 41.625
When I start Tails from USB drive "old" with network unplugged 2:19.045
Then the boot device has safe access rights 5.498
And Tails is running from USB drive "old" 1.048
And there is no persistence partition on USB drive "old" 0.174
And process "udev-watchdog" is running 0.357
And udev-watchdog is monitoring the correct device 0.580
And I unplug USB drive "old" 0.478
After features/support/hooks.rb:330 4.491
After features/support/hooks.rb:100 0.009
Tags: @product
3:5.878
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.209
And I start Tails from USB drive "old" with network unplugged and I login 2:2.984
Then Tails is running from USB drive "old" 0.436
And I create a persistent partition 45.020
And I take note of which tps features are available 5.692
Then a Tails persistence partition exists on USB drive "old" 2.741
And I shutdown Tails and wait for the computer to power off 8.793
After features/support/hooks.rb:330 0.254
After features/support/hooks.rb:100 0.011
Tags: @product
4:22.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.017
Given a computer 0.270
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:29.207
Then Tails is running from USB drive "old" 1.272
And all tps features are active 2.634
When I write some files expected to persist 1.831
# 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.401
And all persistent directories from the old Tails version have safe access rights 2.406
And I take note of which tps features are available 0.532
And I shutdown Tails and wait for the computer to power off 5.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 38.490
After features/support/hooks.rb:330 0.148
After features/support/hooks.rb:100 0.019
Tags: @product
3:21.089
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 16.151
And I log in to a new session 24.152
And I clone USB drive "old" to a new USB drive "to_upgrade" 6.015
And I plug USB drive "to_upgrade" 6.082
When I upgrade Tails to USB drive "to_upgrade" by cloning 2:1.234
Then the running Tails is installed on USB drive "to_upgrade" 27.065
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.198
After features/support/hooks.rb:330 7.041
After features/support/hooks.rb:100 0.000
Tags: @product
3:5.940
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given a computer 0.378
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:49.881
Then all tps features from the old Tails version are active 2.076
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 8.071
And the expected persistent files created with the old Tails version are present in the filesystem 2.220
And all persistent directories from the old Tails version have safe access rights 2.980
After features/support/hooks.rb:330 1.575
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
9:15.576
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 16.655
And no SquashFS delta is installed 0.122
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.895
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.305
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.493
When the network is plugged 0.072
And Tor is ready 37.604
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.798
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 19.377
Given I shutdown Tails and wait for the computer to power off 17.868
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:45.309
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 4.456
And the file system changes introduced in version 6.2~testoverlayfs are present 0.767
And only the 6.2~testoverlayfs SquashFS delta is installed 0.112
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.443
# 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.572
When the network is plugged 0.260
And Tor is ready 23.070
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.935
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 15.935
Given I shutdown Tails and wait for the computer to power off 5.060
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:53.189
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.305
And the file system changes introduced in version 6.3~testoverlayfs are present 0.473
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.316
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.273
When the network is plugged 0.081
And Tor is ready 24.638
Then the Upgrader considers the system as up-to-date 0.332
# 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 28.079
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.619
After features/support/hooks.rb:330 0.979
After features/support/hooks.rb:100 0.023
Tags: @product @automatic_upgrade
54.451
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 10.612
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 3.466
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.263
And the signing key used by the Upgrader is outdated 0.447
But a current signing key is available on our website 0.000
When the network is plugged 0.134
And Tor is ready 36.148
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.377
After features/support/hooks.rb:330 1.535
After features/support/hooks.rb:100 0.000