Project Number Date
test_Tails_ISO_stable-flatpak 55 24 Oct 2026, 19:45

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:25.670 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:1.140
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.019
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.348
When I start Tails from USB drive "old" with network unplugged 44.010
Then the boot device has safe access rights 2.072
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.029
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.177
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.394
After features/support/hooks.rb:108 0.038
Tags: @product
1:26.996
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 49.421
Then Tails is running from USB drive "old" 0.207
And I create a persistent partition 25.037
And I take note of which tps features are available 6.407
Then a Tails persistence partition exists on USB drive "old" 0.482
And I shutdown Tails and wait for the computer to power off 5.332
After features/support/hooks.rb:339 0.373
After features/support/hooks.rb:108 0.005
Tags: @product
1:33.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.025
Then Tails is running from USB drive "old" 0.210
And all tps features are active 7.285
When I write some files expected to persist 1.258
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.125
And all persistence configuration files have safe access rights 0.247
And all persistent directories from the old Tails version have safe access rights 2.192
And I take note of which tps features are available 6.182
And I shutdown Tails and wait for the computer to power off 2.521
# 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.753
After features/support/hooks.rb:339 0.448
After features/support/hooks.rb:108 0.012
Tags: @product
2:14.886
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 without a persistent partition and stopped at Tails Greeter's login screen 8.440
And I log in to a new session 13.164
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.730
And I plug USB drive "to_upgrade" 2.493
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.479
Then the running Tails is installed on USB drive "to_upgrade" 18.346
And I unplug USB drive "to_upgrade" 0.110
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.758
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.688
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.174
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.081
Then all tps features from the old Tails version are active 1.211
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 2.141
And the expected persistent files created with the old Tails version are present in the filesystem 1.100
And all persistent directories from the old Tails version have safe access rights 1.720
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.022
Tags: @product @automatic_upgrade
3:39.199
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.241
And no SquashFS delta is installed 0.101
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.085
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.034
And Tor is ready 11.645
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.337
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.564
Given I shutdown Tails and wait for the computer to power off 7.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.285
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.519
And the file system changes introduced in version 6.2~testoverlayfs are present 0.177
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.211
When the network is plugged 0.046
And Tor is ready 10.465
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.154
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.995
Given I shutdown Tails and wait for the computer to power off 3.885
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.587
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.733
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.194
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.034
And Tor is ready 10.569
Then the Upgrader considers the system as up-to-date 0.106
# 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.530
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.317
After features/support/hooks.rb:339 0.750
After features/support/hooks.rb:108 0.047
Tags: @product @automatic_upgrade
19.856
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 7.990
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.008
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.522
After features/support/hooks.rb:339 1.169
After features/support/hooks.rb:108 0.000