Project Number Date
test_Tails_ISO_web-release-7.8.1 3 03 Jun 2026, 21:19

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:39.576 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:10.656
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.060
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.880
When I start Tails from USB drive "old" with network unplugged 52.069
Then the boot device has safe access rights 2.873
And Tails is running from USB drive "old" 0.240
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.199
After features/support/hooks.rb:335 3.456
After features/support/hooks.rb:104 0.016
Tags: @product
1:29.450
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 55.135
Then Tails is running from USB drive "old" 0.323
And I create a persistent partition 24.592
And I take note of which tps features are available 0.339
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.450
After features/support/hooks.rb:335 0.457
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.663
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.903
Then Tails is running from USB drive "old" 0.308
And all tps features are active 1.325
When I write some files expected to persist 1.393
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 2.120
And I take note of which tps features are available 0.227
And I shutdown Tails and wait for the computer to power off 4.157
# 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.695
After features/support/hooks.rb:335 0.156
After features/support/hooks.rb:104 0.006
Tags: @product
2:14.809
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.471
And I log in to a new session 14.136
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.874
And I plug USB drive "to_upgrade" 2.266
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.681
Then the running Tails is installed on USB drive "to_upgrade" 16.015
And I unplug USB drive "to_upgrade" 0.182
And I unplug USB drive "__internal" 0.181
After features/support/hooks.rb:335 2.248
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.994
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.117
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.223
Then all tps features from the old Tails version are active 0.994
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.424
And the expected persistent files created with the old Tails version are present in the filesystem 1.151
And all persistent directories from the old Tails version have safe access rights 1.859
After features/support/hooks.rb:335 0.885
After features/support/hooks.rb:104 0.007
3:47.577
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.045
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.243
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.016
And Tor is ready 13.554
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.473
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.883
Given I shutdown Tails and wait for the computer to power off 6.840
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.979
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.298
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.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.176
# 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.260
When the network is plugged 0.015
And Tor is ready 11.384
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.256
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.593
Given I shutdown Tails and wait for the computer to power off 8.161
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.190
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.243
And the file system changes introduced in version 6.3~testoverlayfs are present 0.398
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.188
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.237
When the network is plugged 0.017
And Tor is ready 12.175
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.938
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.426
After features/support/hooks.rb:335 0.923
After features/support/hooks.rb:104 0.036
21.425
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.424
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.281
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.397
After features/support/hooks.rb:335 0.876
After features/support/hooks.rb:104 0.000