Project Number Date
test_Tails_ISO_devel 4359 22 Apr 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 13:41.206 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:10.933
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.393
When I start Tails from USB drive "old" with network unplugged 51.658
Then the boot device has safe access rights 3.047
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.067
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:331 1.339
After features/support/hooks.rb:100 0.010
Tags: @product
1:31.509
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 57.249
Then Tails is running from USB drive "old" 0.262
And I create a persistent partition 25.637
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.525
And I shutdown Tails and wait for the computer to power off 7.027
After features/support/hooks.rb:331 0.370
After features/support/hooks.rb:100 0.006
Tags: @product
1:35.503
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.171
Then Tails is running from USB drive "old" 0.311
And all tps features are active 1.238
When I write some files expected to persist 1.452
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.483
And all persistent directories from the old Tails version have safe access rights 2.223
And I take note of which tps features are available 0.259
And I shutdown Tails and wait for the computer to power off 7.006
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 14.096
After features/support/hooks.rb:331 0.354
After features/support/hooks.rb:100 0.017
Tags: @product
2:20.841
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.324
And I log in to a new session 19.080
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.401
Then the running Tails is installed on USB drive "to_upgrade" 16.682
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:331 2.754
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.107
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.679
Then all tps features from the old Tails version are active 0.992
And Tails is running from USB drive "to_upgrade" 0.255
And the boot device has safe access rights 2.678
And the expected persistent files created with the old Tails version are present in the filesystem 1.214
And all persistent directories from the old Tails version have safe access rights 2.218
After features/support/hooks.rb:331 0.753
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
5:19.188
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 9.319
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.429
When the network is plugged 0.027
And Tor is ready 44.012
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.437
Given I shutdown Tails and wait for the computer to power off 19.963
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.037
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.367
And the file system changes introduced in version 6.2~testoverlayfs are present 0.234
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.151
# 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.216
When the network is plugged 0.025
And Tor is ready 22.502
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.442
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.624
Given I shutdown Tails and wait for the computer to power off 17.865
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.065
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.199
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.016
And Tor is ready 20.992
Then the Upgrader considers the system as up-to-date 0.108
# 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.918
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.376
After features/support/hooks.rb:331 1.148
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
29.121
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 8.274
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.042
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 19.946
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.508
After features/support/hooks.rb:331 0.697
After features/support/hooks.rb:100 0.000