Project Number Date
test_Tails_ISO_stable 6699 29 Sep 2026, 11:25

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 11:12.228 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:7.201
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 13.152
When I start Tails from USB drive "old" with network unplugged 50.298
Then the boot device has safe access rights 1.939
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.030
And udev-watchdog is monitoring the correct device 0.222
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.553
After features/support/hooks.rb:108 0.006
Tags: @product
1:20.962
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 48.161
Then Tails is running from USB drive "old" 0.192
And I create a persistent partition 22.948
And I take note of which tps features are available 6.411
Then a Tails persistence partition exists on USB drive "old" 0.515
And I shutdown Tails and wait for the computer to power off 2.645
After features/support/hooks.rb:339 0.356
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.886
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.419
Then Tails is running from USB drive "old" 0.187
And all tps features are active 7.074
When I write some files expected to persist 1.074
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.275
And all persistent directories from the old Tails version have safe access rights 1.723
And I take note of which tps features are available 5.996
And I shutdown Tails and wait for the computer to power off 2.552
# 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" 11.284
After features/support/hooks.rb:339 0.458
After features/support/hooks.rb:108 0.005
Tags: @product
2:23.265
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 21.556
And I log in to a new session 10.208
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.891
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.063
Then the running Tails is installed on USB drive "to_upgrade" 17.060
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.570
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.809
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.008
Then all tps features from the old Tails version are active 0.972
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.133
And the expected persistent files created with the old Tails version are present in the filesystem 0.819
And all persistent directories from the old Tails version have safe access rights 1.570
After features/support/hooks.rb:339 0.898
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:26.392
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.121
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.157
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.245
When the network is plugged 0.026
And Tor is ready 12.205
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.469
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.327
Given I shutdown Tails and wait for the computer to power off 5.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.259
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.874
And the file system changes introduced in version 6.2~testoverlayfs are present 0.148
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.091
# 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.174
When the network is plugged 0.033
And Tor is ready 10.280
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.939
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.959
Given I shutdown Tails and wait for the computer to power off 2.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.684
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 8.063
And the file system changes introduced in version 6.3~testoverlayfs are present 0.294
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.024
And Tor is ready 10.347
Then the Upgrader considers the system as up-to-date 0.075
# 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 3.497
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 0.943
After features/support/hooks.rb:108 0.026
Tags: @product @automatic_upgrade
18.710
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.203
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.037
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.748
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.304
After features/support/hooks.rb:339 1.001
After features/support/hooks.rb:108 0.000