Project Number Date
test_Tails_ISO_devel 4667 09 Oct 2026, 07:39

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:45.015 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:13.209
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 14.644
When I start Tails from USB drive "old" with network unplugged 54.277
Then the boot device has safe access rights 2.447
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.877
After features/support/hooks.rb:108 0.030
Tags: @product
1:24.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 48.890
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 24.295
And I take note of which tps features are available 6.556
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 4.053
After features/support/hooks.rb:339 0.142
After features/support/hooks.rb:108 0.009
Tags: @product
1:37.604
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.643
Then Tails is running from USB drive "old" 0.214
And all tps features are active 8.132
When I write some files expected to persist 1.232
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.989
And I take note of which tps features are available 6.456
And I shutdown Tails and wait for the computer to power off 4.210
# 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.084
After features/support/hooks.rb:339 0.217
After features/support/hooks.rb:108 0.011
Tags: @product
2:16.468
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.793
And I log in to a new session 13.210
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.725
And I plug USB drive "to_upgrade" 2.372
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.468
Then the running Tails is installed on USB drive "to_upgrade" 19.616
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.148
After features/support/hooks.rb:339 1.749
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.502
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.117
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.394
Then all tps features from the old Tails version are active 1.262
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.417
And the expected persistent files created with the old Tails version are present in the filesystem 1.223
And all persistent directories from the old Tails version have safe access rights 1.868
After features/support/hooks.rb:339 0.697
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
3:41.178
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.513
And no SquashFS delta is installed 0.084
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.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.168
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.318
When the network is plugged 0.033
And Tor is ready 13.742
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.359
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.364
Given I shutdown Tails and wait for the computer to power off 5.347
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.571
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.416
And the file system changes introduced in version 6.2~testoverlayfs are present 0.167
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.113
# 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.152
When the network is plugged 0.029
And Tor is ready 11.854
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.384
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.943
Given I shutdown Tails and wait for the computer to power off 2.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.798
Then Tails is running version 6.3~testoverlayfs 0.020
And all tps features are active 8.624
And the file system changes introduced in version 6.3~testoverlayfs are present 0.378
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.205
When the network is plugged 0.035
And Tor is ready 11.048
Then the Upgrader considers the system as up-to-date 0.093
# 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.850
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.447
After features/support/hooks.rb:339 0.833
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.355
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.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 10.313
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.584
After features/support/hooks.rb:339 0.840
After features/support/hooks.rb:108 0.000