Project Number Date
test_Tails_ISO_stable 6636 03 Sep 2026, 18:31

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 12:13.799 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:0.086
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 15.339
When I start Tails from USB drive "old" with network unplugged 40.231
Then the boot device has safe access rights 2.716
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.107
After features/support/hooks.rb:339 1.212
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.449
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 49.564
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 23.804
And I take note of which tps features are available 7.391
Then a Tails persistence partition exists on USB drive "old" 0.658
And I shutdown Tails and wait for the computer to power off 2.663
After features/support/hooks.rb:339 0.415
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.757
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.516
Then Tails is running from USB drive "old" 0.203
And all tps features are active 8.145
When I write some files expected to persist 1.257
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.204
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.933
And I take note of which tps features are available 6.487
And I shutdown Tails and wait for the computer to power off 4.160
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.420
After features/support/hooks.rb:339 0.605
After features/support/hooks.rb:108 0.007
Tags: @product
2:17.091
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.806
And I log in to a new session 12.667
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.858
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.307
Then the running Tails is installed on USB drive "to_upgrade" 18.904
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.724
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.559
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.744
Then all tps features from the old Tails version are active 1.155
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.402
And the expected persistent files created with the old Tails version are present in the filesystem 1.002
And all persistent directories from the old Tails version have safe access rights 1.928
After features/support/hooks.rb:339 0.672
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:8.519
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.735
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.458
When the network is plugged 0.028
And Tor is ready 12.493
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.250
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.813
Given I shutdown Tails and wait for the computer to power off 5.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.915
Then Tails is running version 6.2~testoverlayfs 0.041
And all tps features are active 8.744
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.131
# 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.206
When the network is plugged 0.046
And Tor is ready 10.968
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.275
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.208
Given I shutdown Tails and wait for the computer to power off 4.007
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.725
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 8.399
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.227
When the network is plugged 0.034
And Tor is ready 10.339
Then the Upgrader considers the system as up-to-date 10.482
# 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 3.818
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.326
After features/support/hooks.rb:339 0.904
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
33.335
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.578
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.025
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.536
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.912
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.000