Project Number Date
test_Tails_ISO_devel 4087 25 Nov 2025, 07:56

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 17:14.096 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:20.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.208
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 37.779
When I start Tails from USB drive "old" with network unplugged 1:37.407
Then the boot device has safe access rights 2.997
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.100
And process "udev-watchdog" is running 0.100
And udev-watchdog is monitoring the correct device 0.256
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:331 4.015
After features/support/hooks.rb:100 0.011
Tags: @product
2:10.783
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.199
And I start Tails from USB drive "old" with network unplugged and I login 1:29.544
Then Tails is running from USB drive "old" 0.629
And I create a persistent partition 30.148
And I take note of which tps features are available 1.330
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.156
After features/support/hooks.rb:331 0.225
After features/support/hooks.rb:100 0.019
Tags: @product
2:19.172
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:41.317
Then Tails is running from USB drive "old" 0.809
And all tps features are active 2.061
When I write some files expected to persist 1.628
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.157
And I take note of which tps features are available 0.469
And I shutdown Tails and wait for the computer to power off 10.012
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.875
After features/support/hooks.rb:331 0.400
After features/support/hooks.rb:100 0.021
Tags: @product
2:41.736
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 12.244
And I log in to a new session 17.478
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.232
And I plug USB drive "to_upgrade" 3.073
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.660
Then the running Tails is installed on USB drive "to_upgrade" 21.631
And I unplug USB drive "to_upgrade" 0.209
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 3.773
After features/support/hooks.rb:100 0.000
Tags: @product
1:54.422
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.202
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:44.680
Then all tps features from the old Tails version are active 1.614
And Tails is running from USB drive "to_upgrade" 0.391
And the boot device has safe access rights 3.219
And the expected persistent files created with the old Tails version are present in the filesystem 1.935
And all persistent directories from the old Tails version have safe access rights 2.379
After features/support/hooks.rb:331 1.138
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
5:22.222
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.379
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.294
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.522
When the network is plugged 0.053
And Tor is ready 18.838
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.594
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.656
Given I shutdown Tails and wait for the computer to power off 11.723
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.268
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.433
And the file system changes introduced in version 6.2~testoverlayfs are present 0.281
And only the 6.2~testoverlayfs SquashFS delta is installed 0.064
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.182
# 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.374
When the network is plugged 0.058
And Tor is ready 12.805
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.450
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.454
Given I shutdown Tails and wait for the computer to power off 9.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:39.634
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.974
And the file system changes introduced in version 6.3~testoverlayfs are present 0.491
And only the 6.3~testoverlayfs SquashFS delta is installed 0.087
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.279
When the network is plugged 0.058
And Tor is ready 12.562
Then the Upgrader considers the system as up-to-date 0.209
# 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 7.747
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.516
After features/support/hooks.rb:331 1.199
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
25.314
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 10.398
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.319
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.065
And Tor is ready 13.760
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.620
After features/support/hooks.rb:331 1.131
After features/support/hooks.rb:100 0.000