Project Number Date
test_Tails_ISO_stable 6334 29 Apr 2026, 13:13

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:17.183 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:3.762
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.383
When I start Tails from USB drive "old" with network unplugged 44.279
Then the boot device has safe access rights 3.189
And Tails is running from USB drive "old" 0.261
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.565
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.632
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 59.275
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 24.594
And I take note of which tps features are available 0.949
Then a Tails persistence partition exists on USB drive "old" 0.629
And I shutdown Tails and wait for the computer to power off 8.770
After features/support/hooks.rb:331 0.353
After features/support/hooks.rb:100 0.023
Tags: @product
1:35.357
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.825
Then Tails is running from USB drive "old" 0.320
And all tps features are active 1.331
When I write some files expected to persist 1.594
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.549
And all persistent directories from the old Tails version have safe access rights 2.063
And I take note of which tps features are available 0.184
And I shutdown Tails and wait for the computer to power off 8.245
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.944
After features/support/hooks.rb:331 0.501
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.515
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 without a persistent partition and stopped at Tails Greeter's login screen 8.886
And I log in to a new session 12.723
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.858
And I plug USB drive "to_upgrade" 2.294
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.698
Then the running Tails is installed on USB drive "to_upgrade" 18.760
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.151
After features/support/hooks.rb:331 2.078
After features/support/hooks.rb:100 0.000
Tags: @product
1:20.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.297
Then all tps features from the old Tails version are active 1.294
And Tails is running from USB drive "to_upgrade" 0.282
And the boot device has safe access rights 3.257
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 2.028
After features/support/hooks.rb:331 0.848
After features/support/hooks.rb:100 0.009
4:55.820
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 9.110
And no SquashFS delta is installed 0.099
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.406
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.466
When the network is plugged 0.019
And Tor is ready 24.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.476
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.179
Given I shutdown Tails and wait for the computer to power off 19.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.711
Then Tails is running version 6.2~testoverlayfs 0.022
And all tps features are active 1.300
And the file system changes introduced in version 6.2~testoverlayfs are present 0.266
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.149
# 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.259
When the network is plugged 0.016
And Tor is ready 21.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.386
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.551
Given I shutdown Tails and wait for the computer to power off 17.708
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.586
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.673
And the file system changes introduced in version 6.3~testoverlayfs are present 0.561
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.016
And Tor is ready 22.286
Then the Upgrader considers the system as up-to-date 0.090
# 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 5.398
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.384
After features/support/hooks.rb:331 0.735
After features/support/hooks.rb:100 0.013
29.700
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.026
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.307
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 19.963
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.274
After features/support/hooks.rb:331 0.678
After features/support/hooks.rb:100 0.000