Project Number Date
test_Tails_ISO_devel 4214 05 Feb 2026, 15:17

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:15.726 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.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.069
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.522
When I start Tails from USB drive "old" with network unplugged 58.823
Then the boot device has safe access rights 3.435
And Tails is running from USB drive "old" 0.351
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 3.888
After features/support/hooks.rb:100 0.048
Tags: @product
1:32.179
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 55.876
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 25.803
And I take note of which tps features are available 0.749
Then a Tails persistence partition exists on USB drive "old" 0.575
And I shutdown Tails and wait for the computer to power off 8.817
After features/support/hooks.rb:331 0.262
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.789
Then Tails is running from USB drive "old" 0.339
And all tps features are active 1.227
When I write some files expected to persist 1.362
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.308
And all persistent directories from the old Tails version have safe access rights 1.995
And I take note of which tps features are available 0.200
And I shutdown Tails and wait for the computer to power off 8.961
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.793
After features/support/hooks.rb:331 0.143
After features/support/hooks.rb:100 0.007
Tags: @product
2:16.577
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 9.147
And I log in to a new session 11.972
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.918
And I plug USB drive "to_upgrade" 2.327
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.017
Then the running Tails is installed on USB drive "to_upgrade" 17.922
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 0.844
After features/support/hooks.rb:100 0.000
Tags: @product
1:15.572
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.397
Then all tps features from the old Tails version are active 1.181
And Tails is running from USB drive "to_upgrade" 0.280
And the boot device has safe access rights 3.055
And the expected persistent files created with the old Tails version are present in the filesystem 1.287
And all persistent directories from the old Tails version have safe access rights 2.315
After features/support/hooks.rb:331 0.658
After features/support/hooks.rb:100 0.035
Tags: @product @automatic_upgrade
3:57.971
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.409
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.385
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.097
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.475
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.381
When the network is plugged 0.017
And Tor is ready 13.212
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.736
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.923
Given I shutdown Tails and wait for the computer to power off 9.891
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.404
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 1.520
And the file system changes introduced in version 6.2~testoverlayfs are present 0.371
And only the 6.2~testoverlayfs SquashFS delta is installed 0.071
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.230
When the network is plugged 0.072
And Tor is ready 12.026
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.108
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.243
Given I shutdown Tails and wait for the computer to power off 8.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.290
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.311
And the file system changes introduced in version 6.3~testoverlayfs are present 0.699
And only the 6.3~testoverlayfs SquashFS delta is installed 0.114
# 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.204
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.032
And Tor is ready 11.705
Then the Upgrader considers the system as up-to-date 10.579
# 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.931
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.452
After features/support/hooks.rb:331 1.055
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
21.436
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 7.953
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
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.046
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 11.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.998
After features/support/hooks.rb:331 0.782
After features/support/hooks.rb:100 0.000