Project Number Date
test_Tails_ISO_devel 4281 15 Mar 2026, 11:14

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:31.322 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:23.437
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 15.071
When I start Tails from USB drive "old" with network unplugged 1:3.258
Then the boot device has safe access rights 3.328
And Tails is running from USB drive "old" 0.250
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:331 3.820
After features/support/hooks.rb:100 0.007
Tags: @product
1:30.137
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 59.624
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 24.265
And I take note of which tps features are available 1.017
Then a Tails persistence partition exists on USB drive "old" 0.707
And I shutdown Tails and wait for the computer to power off 4.167
After features/support/hooks.rb:331 0.204
After features/support/hooks.rb:100 0.008
Tags: @product
1:32.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.070
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.368
When I write some files expected to persist 1.717
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.447
And all persistent directories from the old Tails version have safe access rights 2.195
And I take note of which tps features are available 0.210
And I shutdown Tails and wait for the computer to power off 4.106
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.466
After features/support/hooks.rb:331 0.200
After features/support/hooks.rb:100 0.009
Tags: @product
2:19.800
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 without a persistent partition and stopped at Tails Greeter's login screen 8.822
And I log in to a new session 13.566
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.895
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.722
Then the running Tails is installed on USB drive "to_upgrade" 20.163
And I unplug USB drive "to_upgrade" 0.219
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 2.861
After features/support/hooks.rb:100 0.000
Tags: @product
1:21.101
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.094
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.411
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.306
And the boot device has safe access rights 3.358
And the expected persistent files created with the old Tails version are present in the filesystem 1.520
And all persistent directories from the old Tails version have safe access rights 2.272
After features/support/hooks.rb:331 0.738
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:57.593
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.842
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.351
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.432
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.572
When the network is plugged 0.067
And Tor is ready 22.894
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.236
Given I shutdown Tails and wait for the computer to power off 19.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.579
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.227
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.235
When the network is plugged 0.022
And Tor is ready 21.999
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.517
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.371
Given I shutdown Tails and wait for the computer to power off 17.725
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.100
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 1.220
And the file system changes introduced in version 6.3~testoverlayfs are present 0.506
And only the 6.3~testoverlayfs SquashFS delta is installed 0.128
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.280
When the network is plugged 0.019
And Tor is ready 21.825
Then the Upgrader considers the system as up-to-date 0.083
# 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.988
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:331 1.009
After features/support/hooks.rb:100 0.084
Tags: @product @automatic_upgrade
27.083
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 7.703
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.332
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 18.452
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.431
After features/support/hooks.rb:331 0.661
After features/support/hooks.rb:100 0.000