Project Number Date
test_Tails_ISO_stable 6139 11 Feb 2026, 07:58

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 11:11.541 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:14.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.191
When I start Tails from USB drive "old" with network unplugged 57.136
Then the boot device has safe access rights 2.701
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.205
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:331 3.766
After features/support/hooks.rb:100 0.024
Tags: @product
1:24.161
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 51.149
Then Tails is running from USB drive "old" 0.313
And I create a persistent partition 23.605
And I take note of which tps features are available 0.684
Then a Tails persistence partition exists on USB drive "old" 0.492
And I shutdown Tails and wait for the computer to power off 7.864
After features/support/hooks.rb:331 0.166
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.606
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.021
Then Tails is running from USB drive "old" 0.230
And all tps features are active 1.005
When I write some files expected to persist 1.170
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.814
And I take note of which tps features are available 0.177
And I shutdown Tails and wait for the computer to power off 7.986
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.727
After features/support/hooks.rb:331 0.227
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.836
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.348
And I log in to a new session 9.492
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.702
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.266
Then the running Tails is installed on USB drive "to_upgrade" 15.522
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 3.832
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.133
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.295
Then all tps features from the old Tails version are active 0.970
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.533
And the expected persistent files created with the old Tails version are present in the filesystem 1.104
And all persistent directories from the old Tails version have safe access rights 1.928
After features/support/hooks.rb:331 0.645
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:32.783
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 with a persistent partition enabled and logged in 8.123
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.288
When the network is plugged 0.013
And Tor is ready 13.238
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.787
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.606
Given I shutdown Tails and wait for the computer to power off 9.231
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.622
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.218
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.217
When the network is plugged 0.015
And Tor is ready 10.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.141
Given I shutdown Tails and wait for the computer to power off 8.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.934
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
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.128
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.014
And Tor is ready 11.100
Then the Upgrader considers the system as up-to-date 10.566
# 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.066
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.343
After features/support/hooks.rb:331 0.593
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
20.224
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.221
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.581
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.051
After features/support/hooks.rb:331 1.010
After features/support/hooks.rb:100 0.000