Project Number Date
test_Tails_ISO_stable 6444 14 Jun 2026, 11:32

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:46.660 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:9.877
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.032
Given a computer 0.117
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 13.127
When I start Tails from USB drive "old" with network unplugged 52.494
Then the boot device has safe access rights 2.377
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 3.690
After features/support/hooks.rb:108 0.025
Tags: @product
1:25.035
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.026
Given a computer 0.130
And I start Tails from USB drive "old" with network unplugged and I login 52.144
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 23.463
And I take note of which tps features are available 4.178
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 4.390
After features/support/hooks.rb:339 0.303
After features/support/hooks.rb:108 0.019
Tags: @product
1:36.306
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.357
Then Tails is running from USB drive "old" 0.236
And all tps features are active 4.928
When I write some files expected to persist 1.227
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.138
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.865
And I take note of which tps features are available 3.720
And I shutdown Tails and wait for the computer to power off 8.251
# 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" 12.108
After features/support/hooks.rb:339 0.518
After features/support/hooks.rb:108 0.020
Tags: @product
2:9.885
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.016
And I log in to a new session 12.547
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.701
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.116
Then the running Tails is installed on USB drive "to_upgrade" 14.979
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 2.193
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.715
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.129
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.054
Then all tps features from the old Tails version are active 1.052
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.333
And the expected persistent files created with the old Tails version are present in the filesystem 1.080
And all persistent directories from the old Tails version have safe access rights 1.813
After features/support/hooks.rb:339 0.529
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:53.993
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 with a persistent partition enabled and logged in 8.371
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.213
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.014
And Tor is ready 14.154
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.974
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.934
Given I shutdown Tails and wait for the computer to power off 9.673
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.160
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.868
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.188
# 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.178
When the network is plugged 0.016
And Tor is ready 9.482
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 4.248
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.458
Given I shutdown Tails and wait for the computer to power off 8.107
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.671
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.928
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.136
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.012
And Tor is ready 10.361
Then the Upgrader considers the system as up-to-date 10.571
# 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.357
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:339 0.894
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
20.845
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 with a persistent partition enabled and logged in 7.688
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.770
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.070
After features/support/hooks.rb:339 0.875
After features/support/hooks.rb:108 0.000