Project Number Date
test_Tails_ISO_devel 4583 01 Sep 2026, 23:12

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:6.788 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
57.448
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.097
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.124
When I start Tails from USB drive "old" with network unplugged 40.498
Then the boot device has safe access rights 2.111
And Tails is running from USB drive "old" 0.195
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.037
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 3.610
After features/support/hooks.rb:108 0.005
Tags: @product
1:23.646
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 49.734
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 24.049
And I take note of which tps features are available 6.417
Then a Tails persistence partition exists on USB drive "old" 0.551
And I shutdown Tails and wait for the computer to power off 2.572
After features/support/hooks.rb:339 0.233
After features/support/hooks.rb:108 0.008
Tags: @product
1:33.624
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.119
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.776
Then Tails is running from USB drive "old" 0.219
And all tps features are active 7.539
When I write some files expected to persist 1.403
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.274
And all persistent directories from the old Tails version have safe access rights 1.855
And I take note of which tps features are available 6.252
And I shutdown Tails and wait for the computer to power off 2.561
# 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.448
After features/support/hooks.rb:339 0.174
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.031
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.205
And I log in to a new session 12.240
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.686
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.121
Then the running Tails is installed on USB drive "to_upgrade" 18.242
And I unplug USB drive "to_upgrade" 0.141
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 3.764
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.562
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.413
Then all tps features from the old Tails version are active 1.118
And Tails is running from USB drive "to_upgrade" 0.215
And the boot device has safe access rights 2.170
And the expected persistent files created with the old Tails version are present in the filesystem 0.935
And all persistent directories from the old Tails version have safe access rights 1.629
After features/support/hooks.rb:339 0.650
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:32.698
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.179
And no SquashFS delta is installed 0.163
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
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.341
When the network is plugged 0.035
And Tor is ready 13.247
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.317
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.632
Given I shutdown Tails and wait for the computer to power off 5.357
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.240
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.204
And the file system changes introduced in version 6.2~testoverlayfs are present 0.178
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.158
When the network is plugged 0.034
And Tor is ready 10.172
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.430
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.527
Given I shutdown Tails and wait for the computer to power off 3.993
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.315
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.049
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.161
When the network is plugged 0.029
And Tor is ready 11.072
Then the Upgrader considers the system as up-to-date 0.103
# 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.679
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:339 0.642
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
18.776
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 7.971
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.245
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.035
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.451
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.987
After features/support/hooks.rb:339 0.965
After features/support/hooks.rb:108 0.000