Project Number Date
test_Tails_ISO_stable 6517 21 Jul 2026, 17:30

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:11.655 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:16.964
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.813
When I start Tails from USB drive "old" with network unplugged 58.259
Then the boot device has safe access rights 2.941
And Tails is running from USB drive "old" 0.366
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.230
And I unplug USB drive "old" 0.157
After features/support/hooks.rb:339 3.698
After features/support/hooks.rb:108 0.007
Tags: @product
1:31.532
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.067
And I start Tails from USB drive "old" with network unplugged and I login 54.912
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 23.578
And I take note of which tps features are available 3.928
Then a Tails persistence partition exists on USB drive "old" 0.508
And I shutdown Tails and wait for the computer to power off 8.254
After features/support/hooks.rb:339 0.344
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.561
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.416
Then Tails is running from USB drive "old" 0.267
And all tps features are active 4.606
When I write some files expected to persist 1.249
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.347
And all persistent directories from the old Tails version have safe access rights 2.014
And I take note of which tps features are available 4.187
And I shutdown Tails and wait for the computer to power off 4.133
# 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.094
After features/support/hooks.rb:339 0.334
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.175
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.600
And I log in to a new session 12.717
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.196
And I plug USB drive "to_upgrade" 2.295
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.611
Then the running Tails is installed on USB drive "to_upgrade" 16.488
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 0.627
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.955
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.196
Then all tps features from the old Tails version are active 1.116
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.873
And the expected persistent files created with the old Tails version are present in the filesystem 1.289
And all persistent directories from the old Tails version have safe access rights 2.142
After features/support/hooks.rb:339 0.864
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:57.557
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.234
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.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.020
And Tor is ready 12.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.854
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.376
Given I shutdown Tails and wait for the computer to power off 7.628
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.746
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 6.613
And the file system changes introduced in version 6.2~testoverlayfs are present 0.269
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.229
When the network is plugged 0.016
And Tor is ready 11.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.631
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.931
Given I shutdown Tails and wait for the computer to power off 4.123
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.513
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.664
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.132
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.014
And Tor is ready 10.319
Then the Upgrader considers the system as up-to-date 10.534
# 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.305
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 0.987
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
19.908
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 7.416
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.234
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.077
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.977
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.126
After features/support/hooks.rb:339 0.874
After features/support/hooks.rb:108 0.000