Project Number Date
test_Tails_ISO_devel 4462 20 Jun 2026, 11:21

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:37.188 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.218
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.025
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 12.917
When I start Tails from USB drive "old" with network unplugged 41.778
Then the boot device has safe access rights 2.688
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.425
After features/support/hooks.rb:108 0.018
Tags: @product
1:30.035
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.108
And I start Tails from USB drive "old" with network unplugged and I login 52.655
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 24.159
And I take note of which tps features are available 4.018
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 8.279
After features/support/hooks.rb:339 0.290
After features/support/hooks.rb:108 0.016
Tags: @product
1:37.149
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.447
Then Tails is running from USB drive "old" 0.278
And all tps features are active 5.054
When I write some files expected to persist 1.378
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.345
And all persistent directories from the old Tails version have safe access rights 1.779
And I take note of which tps features are available 3.675
And I shutdown Tails and wait for the computer to power off 8.316
# 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.603
After features/support/hooks.rb:339 0.204
After features/support/hooks.rb:108 0.016
Tags: @product
2:9.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.032
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.108
And I log in to a new session 12.127
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.705
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.966
Then the running Tails is installed on USB drive "to_upgrade" 14.924
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:339 1.901
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.902
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.128
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.031
Then all tps features from the old Tails version are active 0.946
And Tails is running from USB drive "to_upgrade" 0.220
And the boot device has safe access rights 2.458
And the expected persistent files created with the old Tails version are present in the filesystem 1.094
And all persistent directories from the old Tails version have safe access rights 2.022
After features/support/hooks.rb:339 0.803
After features/support/hooks.rb:108 0.016
Tags: @product @automatic_upgrade
3:50.007
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.541
And no SquashFS delta is installed 0.090
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.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.220
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.382
When the network is plugged 0.016
And Tor is ready 12.432
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.584
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.070
Given I shutdown Tails and wait for the computer to power off 9.506
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.561
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 4.873
And the file system changes introduced in version 6.2~testoverlayfs are present 0.238
And only the 6.2~testoverlayfs SquashFS delta is installed 0.040
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.240
When the network is plugged 0.016
And Tor is ready 9.601
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.619
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.729
Given I shutdown Tails and wait for the computer to power off 8.102
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.280
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.834
And the file system changes introduced in version 6.3~testoverlayfs are present 0.323
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.123
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.015
And Tor is ready 10.586
Then the Upgrader considers the system as up-to-date 10.498
# 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.412
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.359
After features/support/hooks.rb:339 0.897
After features/support/hooks.rb:108 0.030
Tags: @product @automatic_upgrade
20.541
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.822
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.774
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.623
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.000