Project Number Date
test_Tails_ISO_stable 6515 21 Jul 2026, 11:48

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:53.604 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:3.978
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.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.606
When I start Tails from USB drive "old" with network unplugged 46.012
Then the boot device has safe access rights 2.567
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.244
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:339 1.416
After features/support/hooks.rb:108 0.010
Tags: @product
1:32.583
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login 55.064
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 25.132
And I take note of which tps features are available 4.652
Then a Tails persistence partition exists on USB drive "old" 0.602
And I shutdown Tails and wait for the computer to power off 6.771
After features/support/hooks.rb:339 0.371
After features/support/hooks.rb:108 0.007
Tags: @product
1:40.348
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.383
Then Tails is running from USB drive "old" 0.198
And all tps features are active 5.243
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.165
And all persistence configuration files have safe access rights 0.361
And all persistent directories from the old Tails version have safe access rights 2.026
And I take note of which tps features are available 4.063
And I shutdown Tails and wait for the computer to power off 8.137
# 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.287
After features/support/hooks.rb:339 0.483
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.043
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 without a persistent partition and stopped at Tails Greeter's login screen 7.736
And I log in to a new session 12.166
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.893
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.379
Then the running Tails is installed on USB drive "to_upgrade" 15.258
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.181
After features/support/hooks.rb:339 2.374
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.337
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.460
Then all tps features from the old Tails version are active 1.017
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.466
And the expected persistent files created with the old Tails version are present in the filesystem 1.103
And all persistent directories from the old Tails version have safe access rights 2.016
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:53.463
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.148
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.185
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.018
And Tor is ready 12.720
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.527
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.182
Given I shutdown Tails and wait for the computer to power off 7.026
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.819
Then Tails is running version 6.2~testoverlayfs 0.017
And all tps features are active 5.470
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.021
And Tor is ready 11.201
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.077
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.628
Given I shutdown Tails and wait for the computer to power off 4.132
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.435
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.365
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.314
When the network is plugged 0.015
And Tor is ready 10.064
Then the Upgrader considers the system as up-to-date 10.539
# 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.182
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.299
After features/support/hooks.rb:339 0.971
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
20.850
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.259
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
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.049
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.069
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.169
After features/support/hooks.rb:339 0.878
After features/support/hooks.rb:108 0.000