Project Number Date
test_Tails_ISO_codespell 17 01 Jul 2025, 10:11

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 21:51.411 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:23.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given a computer 0.334
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.059
And I write an old version of the Tails USB image to disk "old" 33.183
When I start Tails from USB drive "old" with network unplugged 1:44.670
Then the boot device has safe access rights 3.425
And Tails is running from USB drive "old" 0.336
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.323
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:330 3.998
After features/support/hooks.rb:100 0.009
Tags: @product
2:32.051
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.235
And I start Tails from USB drive "old" with network unplugged and I login 1:41.424
Then Tails is running from USB drive "old" 0.398
And I create a persistent partition 34.953
And I take note of which tps features are available 2.210
Then a Tails persistence partition exists on USB drive "old" 0.858
And I shutdown Tails and wait for the computer to power off 11.970
After features/support/hooks.rb:330 0.213
After features/support/hooks.rb:100 0.009
Tags: @product
3:10.538
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.239
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:24.928
Then Tails is running from USB drive "old" 0.368
And all tps features are active 2.072
When I write some files expected to persist 2.305
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.232
And all persistence configuration files have safe access rights 0.532
And all persistent directories from the old Tails version have safe access rights 4.660
And I take note of which tps features are available 0.485
And I shutdown Tails and wait for the computer to power off 6.914
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.799
After features/support/hooks.rb:330 0.111
After features/support/hooks.rb:100 0.010
Tags: @product
2:45.525
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.826
And I log in to a new session 21.030
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.339
And I plug USB drive "to_upgrade" 2.457
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.636
Then the running Tails is installed on USB drive "to_upgrade" 30.457
And I unplug USB drive "to_upgrade" 0.504
And I unplug USB drive "__internal" 0.274
After features/support/hooks.rb:330 2.178
After features/support/hooks.rb:100 0.000
Tags: @product
2:39.971
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:27.309
Then all tps features from the old Tails version are active 1.596
And Tails is running from USB drive "to_upgrade" 0.491
And the boot device has safe access rights 4.118
And the expected persistent files created with the old Tails version are present in the filesystem 2.627
And all persistent directories from the old Tails version have safe access rights 3.620
After features/support/hooks.rb:330 1.559
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
7:18.935
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 with a persistent partition enabled and logged in 12.490
And no SquashFS delta is installed 0.286
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.745
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.138
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.631
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.719
When the network is plugged 0.085
And Tor is ready 23.590
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.690
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.938
Given I shutdown Tails and wait for the computer to power off 11.145
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:29.182
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.988
And the file system changes introduced in version 6.2~testoverlayfs are present 0.362
And only the 6.2~testoverlayfs SquashFS delta is installed 0.081
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.332
# 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.365
When the network is plugged 0.078
And Tor is ready 20.215
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 7.367
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 13.971
Given I shutdown Tails and wait for the computer to power off 4.423
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:8.297
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.557
And the file system changes introduced in version 6.3~testoverlayfs are present 0.596
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.312
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.522
When the network is plugged 0.066
And Tor is ready 19.891
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 17.967
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 1.483
After features/support/hooks.rb:330 0.801
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
1:0.650
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 10.640
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 48.790
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.707
After features/support/hooks.rb:330 0.947
After features/support/hooks.rb:100 0.000