Project Number Date
test_Tails_ISO_stable 6199 13 Mar 2026, 00:12

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:45.005 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:18.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.013
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.621
When I start Tails from USB drive "old" with network unplugged 58.622
Then the boot device has safe access rights 3.060
And Tails is running from USB drive "old" 0.337
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.474
After features/support/hooks.rb:100 0.032
Tags: @product
1:29.097
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 57.508
Then Tails is running from USB drive "old" 0.292
And I create a persistent partition 25.639
And I take note of which tps features are available 0.876
Then a Tails persistence partition exists on USB drive "old" 0.582
And I shutdown Tails and wait for the computer to power off 4.121
After features/support/hooks.rb:331 0.291
After features/support/hooks.rb:100 0.007
Tags: @product
1:28.821
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.549
Then Tails is running from USB drive "old" 0.272
And all tps features are active 1.383
When I write some files expected to persist 1.407
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.164
And all persistence configuration files have safe access rights 0.455
And all persistent directories from the old Tails version have safe access rights 1.858
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 4.079
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.381
After features/support/hooks.rb:331 0.560
After features/support/hooks.rb:100 0.008
Tags: @product
2:15.405
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 without a persistent partition and stopped at Tails Greeter's login screen 8.646
And I log in to a new session 12.230
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.853
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.517
Then the running Tails is installed on USB drive "to_upgrade" 17.594
And I unplug USB drive "to_upgrade" 0.147
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:331 2.535
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.926
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.659
Then all tps features from the old Tails version are active 1.187
And Tails is running from USB drive "to_upgrade" 0.284
And the boot device has safe access rights 3.120
And the expected persistent files created with the old Tails version are present in the filesystem 1.445
And all persistent directories from the old Tails version have safe access rights 2.163
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:31.193
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.903
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.343
When the network is plugged 0.019
And Tor is ready 23.046
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.385
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.599
Given I shutdown Tails and wait for the computer to power off 8.365
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.415
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.299
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# 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.271
When the network is plugged 0.019
And Tor is ready 22.813
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.870
Given I shutdown Tails and wait for the computer to power off 12.417
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.535
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.371
And the file system changes introduced in version 6.3~testoverlayfs are present 0.386
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.178
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.198
When the network is plugged 0.014
And Tor is ready 22.373
Then the Upgrader considers the system as up-to-date 0.107
# 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.299
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:331 0.856
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
27.351
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.229
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.044
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 18.326
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.430
After features/support/hooks.rb:331 0.925
After features/support/hooks.rb:100 0.000