Project Number Date
test_Tails_ISO_devel 4481 05 Jul 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 12:15.998 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:9.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.661
When I start Tails from USB drive "old" with network unplugged 51.067
Then the boot device has safe access rights 2.706
And Tails is running from USB drive "old" 0.189
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.298
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:339 1.362
After features/support/hooks.rb:108 0.011
Tags: @product
1:34.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 53.975
Then Tails is running from USB drive "old" 0.224
And I create a persistent partition 26.901
And I take note of which tps features are available 4.431
Then a Tails persistence partition exists on USB drive "old" 0.666
And I shutdown Tails and wait for the computer to power off 7.907
After features/support/hooks.rb:339 0.167
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.345
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.720
Then Tails is running from USB drive "old" 0.363
And all tps features are active 4.904
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.748
And I take note of which tps features are available 3.928
And I shutdown Tails and wait for the computer to power off 8.550
# 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.247
After features/support/hooks.rb:339 0.552
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.940
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 7.926
And I log in to a new session 12.054
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.910
And I plug USB drive "to_upgrade" 2.271
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.636
Then the running Tails is installed on USB drive "to_upgrade" 15.774
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:339 1.989
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.322
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.065
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:8.160
Then all tps features from the old Tails version are active 1.409
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 2.910
And the expected persistent files created with the old Tails version are present in the filesystem 1.314
And all persistent directories from the old Tails version have safe access rights 2.183
After features/support/hooks.rb:339 0.942
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
4:4.592
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.274
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
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.405
When the network is plugged 0.013
And Tor is ready 12.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.043
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.795
Given I shutdown Tails and wait for the computer to power off 11.095
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.439
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.690
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
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.170
# 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.218
When the network is plugged 0.016
And Tor is ready 11.388
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.501
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.731
Given I shutdown Tails and wait for the computer to power off 8.072
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.332
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 6.009
And the file system changes introduced in version 6.3~testoverlayfs are present 0.411
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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.015
And Tor is ready 10.614
Then the Upgrader considers the system as up-to-date 10.507
# 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.446
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.829
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.388
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.306
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.980
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.716
After features/support/hooks.rb:339 0.795
After features/support/hooks.rb:108 0.000