Project Number Date
test_Tails_ISO_stable 6575 12 Aug 2026, 11:25

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 10:53.625 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:12.169
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.007
When I start Tails from USB drive "old" with network unplugged 55.438
Then the boot device has safe access rights 1.837
And Tails is running from USB drive "old" 0.208
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.290
And I unplug USB drive "old" 0.150
After features/support/hooks.rb:339 3.362
After features/support/hooks.rb:108 0.006
Tags: @product
1:19.723
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.099
Then Tails is running from USB drive "old" 0.203
And I create a persistent partition 23.159
And I take note of which tps features are available 5.686
Then a Tails persistence partition exists on USB drive "old" 0.458
And I shutdown Tails and wait for the computer to power off 4.043
After features/support/hooks.rb:339 0.201
After features/support/hooks.rb:108 0.006
Tags: @product
1:27.165
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.962
Then Tails is running from USB drive "old" 0.193
And all tps features are active 7.003
When I write some files expected to persist 0.906
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.130
And all persistence configuration files have safe access rights 0.237
And all persistent directories from the old Tails version have safe access rights 1.408
And I take note of which tps features are available 5.547
And I shutdown Tails and wait for the computer to power off 2.538
# 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.147
After features/support/hooks.rb:339 0.100
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.317
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.111
And I log in to a new session 11.603
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.568
And I plug USB drive "to_upgrade" 2.277
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.052
Then the running Tails is installed on USB drive "to_upgrade" 17.454
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.627
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.598
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.107
Then all tps features from the old Tails version are active 0.953
And Tails is running from USB drive "to_upgrade" 0.165
And the boot device has safe access rights 2.060
And the expected persistent files created with the old Tails version are present in the filesystem 0.836
And all persistent directories from the old Tails version have safe access rights 1.387
After features/support/hooks.rb:339 0.607
After features/support/hooks.rb:108 0.037
3:21.701
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.055
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
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.224
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.291
When the network is plugged 0.031
And Tor is ready 12.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.492
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.747
Given I shutdown Tails and wait for the computer to power off 5.180
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.391
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.674
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.069
# 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.150
When the network is plugged 0.025
And Tor is ready 9.982
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.404
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.738
Given I shutdown Tails and wait for the computer to power off 3.956
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.923
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 6.989
And the file system changes introduced in version 6.3~testoverlayfs are present 0.293
And only the 6.3~testoverlayfs SquashFS delta is installed 0.034
# 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.083
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.152
When the network is plugged 0.035
And Tor is ready 12.682
Then the Upgrader considers the system as up-to-date 0.080
# 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.257
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.318
After features/support/hooks.rb:339 0.609
After features/support/hooks.rb:108 0.017
18.949
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.700
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.567
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.374
After features/support/hooks.rb:339 0.753
After features/support/hooks.rb:108 0.000