Project Number Date
test_Tails_ISO_stable 6274 07 Apr 2026, 18:40

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:24.345 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:15.263
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.373
When I start Tails from USB drive "old" with network unplugged 56.268
Then the boot device has safe access rights 2.822
And Tails is running from USB drive "old" 0.289
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 1.304
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.659
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 54.275
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 23.504
And I take note of which tps features are available 0.752
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.145
After features/support/hooks.rb:331 0.205
After features/support/hooks.rb:100 0.007
Tags: @product
1:25.929
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.775
Then Tails is running from USB drive "old" 0.317
And all tps features are active 1.146
When I write some files expected to persist 1.265
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.463
And all persistent directories from the old Tails version have safe access rights 2.104
And I take note of which tps features are available 0.206
And I shutdown Tails and wait for the computer to power off 4.353
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.053
After features/support/hooks.rb:331 0.366
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.187
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 8.211
And I log in to a new session 16.925
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.856
And I plug USB drive "to_upgrade" 2.236
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.574
Then the running Tails is installed on USB drive "to_upgrade" 17.096
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:331 7.278
After features/support/hooks.rb:100 0.000
Tags: @product
1:22.749
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:15.561
Then all tps features from the old Tails version are active 1.112
And Tails is running from USB drive "to_upgrade" 0.291
And the boot device has safe access rights 2.629
And the expected persistent files created with the old Tails version are present in the filesystem 1.128
And all persistent directories from the old Tails version have safe access rights 1.966
After features/support/hooks.rb:331 0.672
After features/support/hooks.rb:100 0.041
Tags: @product @automatic_upgrade
5:4.594
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 8.508
And no SquashFS delta is installed 0.857
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.496
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.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.341
When the network is plugged 0.020
And Tor is ready 46.408
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.362
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.267
Given I shutdown Tails and wait for the computer to power off 13.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.555
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.149
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
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.146
# 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.205
When the network is plugged 0.016
And Tor is ready 20.609
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.050
Given I shutdown Tails and wait for the computer to power off 17.303
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.571
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.017
And Tor is ready 20.851
Then the Upgrader considers the system as up-to-date 0.110
# 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.511
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.510
After features/support/hooks.rb:331 0.960
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
27.961
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.833
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.790
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.066
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 18.821
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
After features/support/hooks.rb:331 0.791
After features/support/hooks.rb:100 0.000