Project Number Date
test_Tails_ISO_stable 6346 02 May 2026, 11:16

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:1.012 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:10.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.111
When I start Tails from USB drive "old" with network unplugged 52.801
Then the boot device has safe access rights 2.663
And Tails is running from USB drive "old" 0.265
And there is no persistence partition on USB drive "old" 0.036
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.722
After features/support/hooks.rb:100 0.007
Tags: @product
1:19.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 51.712
Then Tails is running from USB drive "old" 0.273
And I create a persistent partition 23.567
And I take note of which tps features are available 0.640
Then a Tails persistence partition exists on USB drive "old" 0.470
And I shutdown Tails and wait for the computer to power off 2.725
After features/support/hooks.rb:331 0.404
After features/support/hooks.rb:100 0.006
Tags: @product
1:18.700
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.818
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.026
When I write some files expected to persist 1.147
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 1.762
And I take note of which tps features are available 0.155
And I shutdown Tails and wait for the computer to power off 4.129
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.815
After features/support/hooks.rb:331 0.129
After features/support/hooks.rb:100 0.007
Tags: @product
2:8.664
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.391
And I log in to a new session 11.948
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.807
And I plug USB drive "to_upgrade" 2.211
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.194
Then the running Tails is installed on USB drive "to_upgrade" 14.842
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 2.077
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.225
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.447
Then all tps features from the old Tails version are active 0.944
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.547
And the expected persistent files created with the old Tails version are present in the filesystem 1.124
And all persistent directories from the old Tails version have safe access rights 1.892
After features/support/hooks.rb:331 0.571
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:31.829
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.100
And no SquashFS delta is installed 0.056
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.238
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.327
When the network is plugged 0.014
And Tor is ready 20.350
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.429
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.919
Given I shutdown Tails and wait for the computer to power off 19.823
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.928
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.079
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.066
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.186
When the network is plugged 0.015
And Tor is ready 21.259
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.453
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.963
Given I shutdown Tails and wait for the computer to power off 18.474
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.232
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.075
And the file system changes introduced in version 6.3~testoverlayfs are present 0.300
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.194
When the network is plugged 0.018
And Tor is ready 21.724
Then the Upgrader considers the system as up-to-date 0.123
# 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.236
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.366
After features/support/hooks.rb:331 0.640
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
24.812
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.278
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 16.820
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
After features/support/hooks.rb:331 0.932
After features/support/hooks.rb:100 0.000