Project Number Date
test_Tails_ISO_add-team-sprint-template 1 21 May 2026, 12:40

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:22.625 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:12.875
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 14.062
When I start Tails from USB drive "old" with network unplugged 54.240
Then the boot device has safe access rights 2.778
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:335 1.900
After features/support/hooks.rb:104 0.006
Tags: @product
1:37.185
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 58.367
Then Tails is running from USB drive "old" 0.312
And I create a persistent partition 28.826
And I take note of which tps features are available 0.386
Then a Tails persistence partition exists on USB drive "old" 0.633
And I shutdown Tails and wait for the computer to power off 8.595
After features/support/hooks.rb:335 0.139
After features/support/hooks.rb:104 0.008
Tags: @product
1:35.264
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.220
Then Tails is running from USB drive "old" 0.348
And all tps features are active 1.602
When I write some files expected to persist 1.636
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.214
And all persistence configuration files have safe access rights 0.371
And all persistent directories from the old Tails version have safe access rights 2.133
And I take note of which tps features are available 0.196
And I shutdown Tails and wait for the computer to power off 6.972
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 13.501
After features/support/hooks.rb:335 0.651
After features/support/hooks.rb:104 0.009
Tags: @product
2:17.679
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.193
And I log in to a new session 15.141
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.797
And I plug USB drive "to_upgrade" 2.291
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.515
Then the running Tails is installed on USB drive "to_upgrade" 17.371
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.208
After features/support/hooks.rb:335 2.515
After features/support/hooks.rb:104 0.000
Tags: @product
1:21.634
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.104
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.410
Then all tps features from the old Tails version are active 1.477
And Tails is running from USB drive "to_upgrade" 0.287
And the boot device has safe access rights 3.501
And the expected persistent files created with the old Tails version are present in the filesystem 1.547
And all persistent directories from the old Tails version have safe access rights 2.306
After features/support/hooks.rb:335 0.688
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
3:57.076
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.664
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
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.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.676
When the network is plugged 0.020
And Tor is ready 13.762
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.050
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.183
Given I shutdown Tails and wait for the computer to power off 9.966
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.184
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.421
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.056
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.245
When the network is plugged 0.022
And Tor is ready 10.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.302
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.397
Given I shutdown Tails and wait for the computer to power off 7.108
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.186
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.224
And the file system changes introduced in version 6.3~testoverlayfs are present 0.536
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.242
When the network is plugged 0.026
And Tor is ready 11.601
Then the Upgrader considers the system as up-to-date 10.681
# 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.271
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.501
After features/support/hooks.rb:335 1.054
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
20.910
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.964
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
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.018
And Tor is ready 10.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.068
After features/support/hooks.rb:335 0.961
After features/support/hooks.rb:104 0.000