Project Number Date
test_Tails_ISO_devel 4473 30 Jun 2026, 07:56

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:59.556 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:11.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.066
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 14.340
When I start Tails from USB drive "old" with network unplugged 52.339
Then the boot device has safe access rights 2.770
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 1.385
After features/support/hooks.rb:108 0.005
Tags: @product
1:32.124
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 54.188
Then Tails is running from USB drive "old" 0.305
And I create a persistent partition 25.014
And I take note of which tps features are available 3.798
Then a Tails persistence partition exists on USB drive "old" 0.519
And I shutdown Tails and wait for the computer to power off 8.238
After features/support/hooks.rb:339 0.298
After features/support/hooks.rb:108 0.007
Tags: @product
1:36.347
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.866
Then Tails is running from USB drive "old" 0.225
And all tps features are active 4.806
When I write some files expected to persist 1.181
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.991
And I take note of which tps features are available 3.814
And I shutdown Tails and wait for the computer to power off 8.182
# 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.776
After features/support/hooks.rb:339 0.556
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.430
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 without a persistent partition and stopped at Tails Greeter's login screen 8.342
And I log in to a new session 13.313
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.798
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.882
Then the running Tails is installed on USB drive "to_upgrade" 14.587
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.142
After features/support/hooks.rb:339 2.042
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.130
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.147
Then all tps features from the old Tails version are active 0.952
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.661
And the expected persistent files created with the old Tails version are present in the filesystem 1.188
And all persistent directories from the old Tails version have safe access rights 1.897
After features/support/hooks.rb:339 0.560
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:57.561
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 8.292
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.334
When the network is plugged 0.017
And Tor is ready 12.563
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.617
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.664
Given I shutdown Tails and wait for the computer to power off 9.628
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.358
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.744
And the file system changes introduced in version 6.2~testoverlayfs are present 0.364
And only the 6.2~testoverlayfs SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.217
When the network is plugged 0.018
And Tor is ready 10.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.327
Given I shutdown Tails and wait for the computer to power off 8.047
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.900
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.940
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.015
And Tor is ready 10.137
Then the Upgrader considers the system as up-to-date 10.554
# 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.669
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.409
After features/support/hooks.rb:339 0.908
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.707
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.589
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.049
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 8.442
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.348
After features/support/hooks.rb:339 1.051
After features/support/hooks.rb:108 0.000