Project Number Date
test_Tails_ISO_stable 6289 12 Apr 2026, 11:33

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 13:14.431 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
1:16.646
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.247
When I start Tails from USB drive "old" with network unplugged 57.597
Then the boot device has safe access rights 3.021
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:331 3.471
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.760
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.079
And I start Tails from USB drive "old" with network unplugged and I login 57.114
Then Tails is running from USB drive "old" 0.251
And I create a persistent partition 25.609
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.641
And I shutdown Tails and wait for the computer to power off 4.344
After features/support/hooks.rb:331 0.110
After features/support/hooks.rb:100 0.009
Tags: @product
1:34.015
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.641
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.156
When I write some files expected to persist 1.357
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.453
And all persistent directories from the old Tails version have safe access rights 2.054
And I take note of which tps features are available 0.213
And I shutdown Tails and wait for the computer to power off 8.657
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.925
After features/support/hooks.rb:331 0.348
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.271
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.598
And I log in to a new session 13.583
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.961
And I plug USB drive "to_upgrade" 2.354
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.358
Then the running Tails is installed on USB drive "to_upgrade" 17.110
And I unplug USB drive "to_upgrade" 0.153
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 2.198
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.444
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.596
Then all tps features from the old Tails version are active 1.421
And Tails is running from USB drive "to_upgrade" 0.380
And the boot device has safe access rights 3.081
And the expected persistent files created with the old Tails version are present in the filesystem 1.536
And all persistent directories from the old Tails version have safe access rights 2.322
After features/support/hooks.rb:331 0.819
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:33.709
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 9.069
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.327
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.324
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.499
When the network is plugged 0.025
And Tor is ready 23.739
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.513
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.422
Given I shutdown Tails and wait for the computer to power off 15.721
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.919
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.322
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.148
# 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.265
When the network is plugged 0.017
And Tor is ready 21.531
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.531
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.696
Given I shutdown Tails and wait for the computer to power off 13.736
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.329
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.093
And the file system changes introduced in version 6.3~testoverlayfs are present 0.457
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.360
When the network is plugged 0.016
And Tor is ready 20.878
Then the Upgrader considers the system as up-to-date 0.116
# 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 4.513
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.475
After features/support/hooks.rb:331 0.833
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
50.584
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.183
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 41.584
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
After features/support/hooks.rb:331 0.627
After features/support/hooks.rb:100 0.000