Project Number Date
test_Tails_ISO_devel 4233 16 Feb 2026, 11:49

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:0.139 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.549
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.579
When I start Tails from USB drive "old" with network unplugged 43.902
Then the boot device has safe access rights 3.245
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 3.708
After features/support/hooks.rb:100 0.033
Tags: @product
1:30.294
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 56.192
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 23.923
And I take note of which tps features are available 0.724
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 8.532
After features/support/hooks.rb:331 0.590
After features/support/hooks.rb:100 0.011
Tags: @product
1:30.935
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.143
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.011
Then Tails is running from USB drive "old" 0.316
And all tps features are active 1.291
When I write some files expected to persist 1.368
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 1.983
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 8.130
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.976
After features/support/hooks.rb:331 0.412
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.917
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.456
And I log in to a new session 10.294
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.839
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.641
Then the running Tails is installed on USB drive "to_upgrade" 16.054
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.226
After features/support/hooks.rb:331 2.183
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.988
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.809
Then all tps features from the old Tails version are active 0.964
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.625
And the expected persistent files created with the old Tails version are present in the filesystem 1.259
And all persistent directories from the old Tails version have safe access rights 2.032
After features/support/hooks.rb:331 0.723
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:12.571
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.893
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.280
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.372
When the network is plugged 0.019
And Tor is ready 43.299
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.399
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.210
Given I shutdown Tails and wait for the computer to power off 9.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.141
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.193
And the file system changes introduced in version 6.2~testoverlayfs are present 0.290
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.220
When the network is plugged 0.015
And Tor is ready 12.015
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.772
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.232
Given I shutdown Tails and wait for the computer to power off 4.208
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.725
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.265
And the file system changes introduced in version 6.3~testoverlayfs are present 0.507
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.173
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.020
And Tor is ready 10.407
Then the Upgrader considers the system as up-to-date 10.599
# 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.242
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.373
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
19.882
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.756
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.293
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.971
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.750
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.000