Project Number Date
test_Tails_ISO_devel 4501 20 Jul 2026, 17:59

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:53.940 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:4.306
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.856
When I start Tails from USB drive "old" with network unplugged 45.932
Then the boot device has safe access rights 2.783
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.144
After features/support/hooks.rb:339 1.466
After features/support/hooks.rb:108 0.028
Tags: @product
1:30.992
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 53.650
Then Tails is running from USB drive "old" 0.230
And I create a persistent partition 25.210
And I take note of which tps features are available 4.549
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 6.759
After features/support/hooks.rb:339 0.419
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.752
Then Tails is running from USB drive "old" 0.233
And all tps features are active 5.686
When I write some files expected to persist 1.468
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.184
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 2.115
And I take note of which tps features are available 3.878
And I shutdown Tails and wait for the computer to power off 8.311
# 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.121
After features/support/hooks.rb:339 0.175
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.208
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 without a persistent partition and stopped at Tails Greeter's login screen 7.842
And I log in to a new session 12.532
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.724
And I plug USB drive "to_upgrade" 2.210
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.095
Then the running Tails is installed on USB drive "to_upgrade" 15.518
And I unplug USB drive "to_upgrade" 0.150
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 2.109
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.348
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.246
Then all tps features from the old Tails version are active 0.939
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.577
And the expected persistent files created with the old Tails version are present in the filesystem 1.209
And all persistent directories from the old Tails version have safe access rights 2.050
After features/support/hooks.rb:339 0.969
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:51.567
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.209
And no SquashFS delta is installed 0.115
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
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.302
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.344
When the network is plugged 0.017
And Tor is ready 14.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.696
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.850
Given I shutdown Tails and wait for the computer to power off 6.871
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.180
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.248
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.221
When the network is plugged 0.017
And Tor is ready 11.350
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.997
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.296
Given I shutdown Tails and wait for the computer to power off 4.056
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.115
Then Tails is running version 6.3~testoverlayfs 0.026
And all tps features are active 5.238
And the file system changes introduced in version 6.3~testoverlayfs are present 0.356
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.016
And Tor is ready 10.578
Then the Upgrader considers the system as up-to-date 10.625
# 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.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.397
After features/support/hooks.rb:339 0.860
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
21.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.250
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.103
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.969
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.218
After features/support/hooks.rb:339 0.873
After features/support/hooks.rb:108 0.000