Project Number Date
test_Tails_ISO_stable 6179 01 Mar 2026, 11:09

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:7.346 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:2.922
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.205
When I start Tails from USB drive "old" with network unplugged 45.119
Then the boot device has safe access rights 2.846
And Tails is running from USB drive "old" 0.226
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 1.475
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.490
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 52.895
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 22.918
And I take note of which tps features are available 0.708
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.102
After features/support/hooks.rb:331 0.447
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.596
Then Tails is running from USB drive "old" 0.222
And all tps features are active 1.178
When I write some files expected to persist 1.396
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.178
And all persistence configuration files have safe access rights 0.480
And all persistent directories from the old Tails version have safe access rights 1.935
And I take note of which tps features are available 0.212
And I shutdown Tails and wait for the computer to power off 7.972
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.954
After features/support/hooks.rb:331 0.128
After features/support/hooks.rb:100 0.006
Tags: @product
2:11.073
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.491
And I log in to a new session 11.121
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.817
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.608
Then the running Tails is installed on USB drive "to_upgrade" 15.520
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:331 2.316
After features/support/hooks.rb:100 0.000
Tags: @product
1:8.992
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.706
Then all tps features from the old Tails version are active 1.127
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.729
And the expected persistent files created with the old Tails version are present in the filesystem 1.131
And all persistent directories from the old Tails version have safe access rights 1.969
After features/support/hooks.rb:331 0.713
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:28.691
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.201
And no SquashFS delta is installed 0.072
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.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.191
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.383
When the network is plugged 0.018
And Tor is ready 19.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.354
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.598
Given I shutdown Tails and wait for the computer to power off 18.576
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.871
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.218
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.193
When the network is plugged 0.022
And Tor is ready 21.948
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.447
Given I shutdown Tails and wait for the computer to power off 17.159
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.227
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.070
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.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.112
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.188
When the network is plugged 0.015
And Tor is ready 20.421
Then the Upgrader considers the system as up-to-date 0.088
# 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.838
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:331 0.729
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
23.997
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.461
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.015
And Tor is ready 15.756
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.419
After features/support/hooks.rb:331 0.761
After features/support/hooks.rb:100 0.000