Project Number Date
test_Tails_ISO_devel 4313 02 Apr 2026, 11:29

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:29.005 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:11.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 14.158
When I start Tails from USB drive "old" with network unplugged 53.239
Then the boot device has safe access rights 2.484
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.517
After features/support/hooks.rb:100 0.029
Tags: @product
1:26.486
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 54.037
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 23.933
And I take note of which tps features are available 0.747
Then a Tails persistence partition exists on USB drive "old" 0.635
And I shutdown Tails and wait for the computer to power off 6.792
After features/support/hooks.rb:331 0.373
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.322
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.988
Then Tails is running from USB drive "old" 0.236
And all tps features are active 1.041
When I write some files expected to persist 1.256
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.557
And all persistent directories from the old Tails version have safe access rights 2.016
And I take note of which tps features are available 0.152
And I shutdown Tails and wait for the computer to power off 8.288
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.567
After features/support/hooks.rb:331 0.502
After features/support/hooks.rb:100 0.007
Tags: @product
2:21.301
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.097
And I log in to a new session 17.342
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.003
And I plug USB drive "to_upgrade" 2.225
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:35.837
Then the running Tails is installed on USB drive "to_upgrade" 16.485
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.165
After features/support/hooks.rb:331 3.127
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.196
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.147
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.610
Then all tps features from the old Tails version are active 1.091
And Tails is running from USB drive "to_upgrade" 0.274
And the boot device has safe access rights 2.654
And the expected persistent files created with the old Tails version are present in the filesystem 1.311
And all persistent directories from the old Tails version have safe access rights 3.105
After features/support/hooks.rb:331 0.700
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:13.459
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.557
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.020
And Tor is ready 43.182
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.425
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.430
Given I shutdown Tails and wait for the computer to power off 24.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.552
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.126
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.204
When the network is plugged 0.013
And Tor is ready 20.521
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.996
Given I shutdown Tails and wait for the computer to power off 17.217
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.308
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.390
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.208
When the network is plugged 0.016
And Tor is ready 20.478
Then the Upgrader considers the system as up-to-date 0.097
# 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.114
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.440
After features/support/hooks.rb:331 0.891
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
30.573
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.155
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.303
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.041
And Tor is ready 21.604
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
After features/support/hooks.rb:331 0.678
After features/support/hooks.rb:100 0.000