Project Number Date
test_Tails_ISO_stable 6241 27 Mar 2026, 17:35

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:59.679 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:8.109
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.859
When I start Tails from USB drive "old" with network unplugged 49.628
Then the boot device has safe access rights 2.885
And Tails is running from USB drive "old" 0.238
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.486
After features/support/hooks.rb:100 0.007
Tags: @product
1:29.157
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 55.540
Then Tails is running from USB drive "old" 0.326
And I create a persistent partition 23.717
And I take note of which tps features are available 0.806
Then a Tails persistence partition exists on USB drive "old" 0.554
And I shutdown Tails and wait for the computer to power off 8.135
After features/support/hooks.rb:331 0.255
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.505
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.374
When I write some files expected to persist 1.242
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.419
And all persistent directories from the old Tails version have safe access rights 2.173
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 8.295
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.227
After features/support/hooks.rb:331 0.437
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.288
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 8.570
And I log in to a new session 13.495
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.774
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.249
Then the running Tails is installed on USB drive "to_upgrade" 15.572
And I unplug USB drive "to_upgrade" 0.216
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 2.669
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.101
Then all tps features from the old Tails version are active 0.938
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.390
And the expected persistent files created with the old Tails version are present in the filesystem 1.053
And all persistent directories from the old Tails version have safe access rights 1.919
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
5:1.318
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.595
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.015
And Tor is ready 20.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.435
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.902
Given I shutdown Tails and wait for the computer to power off 19.073
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.997
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.292
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
And only the 6.2~testoverlayfs SquashFS delta is installed 0.065
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.231
When the network is plugged 0.014
And Tor is ready 22.712
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.352
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.117
Given I shutdown Tails and wait for the computer to power off 17.407
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.417
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.054
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.015
And Tor is ready 40.736
Then the Upgrader considers the system as up-to-date 0.104
# 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.358
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.416
After features/support/hooks.rb:331 0.705
After features/support/hooks.rb:100 0.022
Tags: @product @automatic_upgrade
27.166
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.034
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.365
After features/support/hooks.rb:331 0.898
After features/support/hooks.rb:100 0.000