Project Number Date
test_Tails_ISO_stable 6450 16 Jun 2026, 16:57

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 12:21.762 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:0.914
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 13.657
When I start Tails from USB drive "old" with network unplugged 42.441
Then the boot device has safe access rights 2.891
And Tails is running from USB drive "old" 0.264
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.215
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.366
After features/support/hooks.rb:108 0.018
Tags: @product
1:37.928
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.217
And I start Tails from USB drive "old" with network unplugged and I login 57.851
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.579
And I take note of which tps features are available 4.604
Then a Tails persistence partition exists on USB drive "old" 0.592
And I shutdown Tails and wait for the computer to power off 8.818
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.016
Tags: @product
1:47.591
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.127
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.154
Then Tails is running from USB drive "old" 0.268
And all tps features are active 5.692
When I write some files expected to persist 1.604
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.335
And all persistent directories from the old Tails version have safe access rights 2.112
And I take note of which tps features are available 4.374
And I shutdown Tails and wait for the computer to power off 8.579
# 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" 13.163
After features/support/hooks.rb:339 0.269
After features/support/hooks.rb:108 0.033
Tags: @product
2:12.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.554
And I log in to a new session 12.400
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.809
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.147
Then the running Tails is installed on USB drive "to_upgrade" 15.821
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.958
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.557
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.126
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.592
Then all tps features from the old Tails version are active 1.103
And Tails is running from USB drive "to_upgrade" 0.244
And the boot device has safe access rights 2.921
And the expected persistent files created with the old Tails version are present in the filesystem 1.254
And all persistent directories from the old Tails version have safe access rights 2.312
After features/support/hooks.rb:339 0.720
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
4:4.540
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.105
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.319
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.019
And Tor is ready 14.072
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.138
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.494
Given I shutdown Tails and wait for the computer to power off 11.578
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.072
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 5.559
And the file system changes introduced in version 6.2~testoverlayfs are present 0.305
And only the 6.2~testoverlayfs SquashFS delta is installed 0.067
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.214
When the network is plugged 0.021
And Tor is ready 9.918
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.485
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.128
Given I shutdown Tails and wait for the computer to power off 7.050
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.159
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.727
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.016
And Tor is ready 9.822
Then the Upgrader considers the system as up-to-date 10.715
# 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.328
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:339 0.910
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
20.970
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.401
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the signing key used by the Upgrader is outdated 0.038
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 10.530
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.643
After features/support/hooks.rb:339 0.793
After features/support/hooks.rb:108 0.000