Project Number Date
test_Tails_ISO_stable 6299 14 Apr 2026, 19: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:51.912 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.193
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 14.951
When I start Tails from USB drive "old" with network unplugged 50.248
Then the boot device has safe access rights 3.057
And Tails is running from USB drive "old" 0.324
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.271
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.455
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.379
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 57.805
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 24.541
And I take note of which tps features are available 0.764
Then a Tails persistence partition exists on USB drive "old" 0.588
And I shutdown Tails and wait for the computer to power off 8.314
After features/support/hooks.rb:331 0.535
After features/support/hooks.rb:100 0.009
Tags: @product
1:31.134
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.107
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.343
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.529
And all persistent directories from the old Tails version have safe access rights 2.052
And I take note of which tps features are available 0.191
And I shutdown Tails and wait for the computer to power off 8.035
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.861
After features/support/hooks.rb:331 0.231
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.537
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.006
And I log in to a new session 12.748
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.791
And I plug USB drive "to_upgrade" 2.234
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.194
Then the running Tails is installed on USB drive "to_upgrade" 18.255
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:331 2.288
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.181
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.061
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.190
Then all tps features from the old Tails version are active 1.045
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.714
And the expected persistent files created with the old Tails version are present in the filesystem 1.578
And all persistent directories from the old Tails version have safe access rights 2.335
After features/support/hooks.rb:331 0.543
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
4:42.372
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 8.716
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.202
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.310
When the network is plugged 0.013
And Tor is ready 22.290
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.486
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.135
Given I shutdown Tails and wait for the computer to power off 20.781
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.379
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 2.013
And the file system changes introduced in version 6.2~testoverlayfs are present 0.310
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.311
When the network is plugged 0.019
And Tor is ready 20.713
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.439
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 8.551
Given I shutdown Tails and wait for the computer to power off 8.201
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.542
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.231
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.063
# 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.154
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.016
And Tor is ready 22.322
Then the Upgrader considers the system as up-to-date 0.182
# 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.402
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.435
After features/support/hooks.rb:331 0.802
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
27.114
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 7.957
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 18.353
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.371
After features/support/hooks.rb:331 0.653
After features/support/hooks.rb:100 0.000