Project Number Date
test_Tails_ISO_devel 4635 24 Sep 2026, 15:11

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 13:56.973 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:5.286
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.093
And I create a 7200 MiB disk named "old" 0.027
And I plug USB drive "old" 1.031
And I write an old version of the Tails USB image to disk "old" 13.557
When I start Tails from USB drive "old" with network unplugged 47.108
Then the boot device has safe access rights 2.754
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.808
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.969
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 "old" with network unplugged and I login 50.028
Then Tails is running from USB drive "old" 0.333
And I create a persistent partition 24.971
And I take note of which tps features are available 7.029
Then a Tails persistence partition exists on USB drive "old" 0.599
And I shutdown Tails and wait for the computer to power off 3.921
After features/support/hooks.rb:339 0.410
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.437
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.523
Then Tails is running from USB drive "old" 0.220
And all tps features are active 8.426
When I write some files expected to persist 1.088
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.117
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.661
And I take note of which tps features are available 6.001
And I shutdown Tails and wait for the computer to power off 5.236
# 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.747
After features/support/hooks.rb:339 0.375
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.659
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 without a persistent partition and stopped at Tails Greeter's login screen 8.466
And I log in to a new session 11.684
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.777
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.952
Then the running Tails is installed on USB drive "to_upgrade" 20.220
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.174
After features/support/hooks.rb:339 2.060
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.225
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.233
Then all tps features from the old Tails version are active 1.258
And Tails is running from USB drive "to_upgrade" 0.252
And the boot device has safe access rights 2.545
And the expected persistent files created with the old Tails version are present in the filesystem 1.046
And all persistent directories from the old Tails version have safe access rights 1.797
After features/support/hooks.rb:339 0.998
After features/support/hooks.rb:108 0.020
Tags: @product @automatic_upgrade
5:55.294
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.491
And no SquashFS delta is installed 0.091
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.260
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.514
When the network is plugged 0.050
And Tor is ready 13.515
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.878
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.165
Given I shutdown Tails and wait for the computer to power off 7.041
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.282
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.839
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.231
# 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.296
When the network is plugged 0.094
And Tor is ready 11.028
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2:3.208
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.438
Given I shutdown Tails and wait for the computer to power off 4.179
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.230
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.913
And the file system changes introduced in version 6.3~testoverlayfs are present 0.403
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.191
When the network is plugged 0.034
And Tor is ready 10.762
Then the Upgrader considers the system as up-to-date 10.416
# 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.633
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.301
After features/support/hooks.rb:339 0.737
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.100
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 with a persistent partition enabled and logged in 8.254
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.048
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.614
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.904
After features/support/hooks.rb:339 0.567
After features/support/hooks.rb:108 0.000