Project Number Date
test_Tails_ISO_stable 6587 18 Aug 2026, 07:26

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:16.353 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
59.916
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.322
When I start Tails from USB drive "old" with network unplugged 42.610
Then the boot device has safe access rights 2.323
And Tails is running from USB drive "old" 0.182
And there is no persistence partition on USB drive "old" 0.081
And process "udev-watchdog" is running 0.029
And udev-watchdog is monitoring the correct device 0.138
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.799
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.861
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 1.541
And I start Tails from USB drive "old" with network unplugged and I login 48.507
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 23.296
And I take note of which tps features are available 6.484
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 5.220
After features/support/hooks.rb:339 0.499
After features/support/hooks.rb:108 0.015
Tags: @product
1:33.874
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.484
Then Tails is running from USB drive "old" 0.281
And all tps features are active 7.447
When I write some files expected to persist 0.974
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.270
And all persistent directories from the old Tails version have safe access rights 1.357
And I take note of which tps features are available 5.955
And I shutdown Tails and wait for the computer to power off 2.709
# 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.072
After features/support/hooks.rb:339 0.418
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.158
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 8.208
And I log in to a new session 11.203
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.623
And I plug USB drive "to_upgrade" 2.217
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.671
Then the running Tails is installed on USB drive "to_upgrade" 17.993
And I unplug USB drive "to_upgrade" 0.113
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.479
After features/support/hooks.rb:108 0.000
Tags: @product
1:8.238
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.456
Then all tps features from the old Tails version are active 1.063
And Tails is running from USB drive "to_upgrade" 0.223
And the boot device has safe access rights 1.954
And the expected persistent files created with the old Tails version are present in the filesystem 0.863
And all persistent directories from the old Tails version have safe access rights 1.602
After features/support/hooks.rb:339 0.938
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:37.684
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 8.261
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.035
And Tor is ready 12.483
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.378
Given I shutdown Tails and wait for the computer to power off 5.399
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.708
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.589
And the file system changes introduced in version 6.2~testoverlayfs are present 0.201
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.111
# 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.159
When the network is plugged 0.039
And Tor is ready 10.326
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.335
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.419
Given I shutdown Tails and wait for the computer to power off 2.606
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.289
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.672
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.159
When the network is plugged 0.024
And Tor is ready 10.324
Then the Upgrader considers the system as up-to-date 10.504
# 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.420
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:339 0.636
After features/support/hooks.rb:108 0.021
Tags: @product @automatic_upgrade
19.619
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.924
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 9.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.366
After features/support/hooks.rb:339 0.564
After features/support/hooks.rb:108 0.000