Project Number Date
test_Tails_ISO_devel 4650 01 Oct 2026, 11:04

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 10:47.713 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:9.244
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.042
And I write an old version of the Tails USB image to disk "old" 13.045
When I start Tails from USB drive "old" with network unplugged 52.506
Then the boot device has safe access rights 2.042
And Tails is running from USB drive "old" 0.140
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.121
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.821
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.227
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 45.517
Then Tails is running from USB drive "old" 0.191
And I create a persistent partition 21.427
And I take note of which tps features are available 5.588
Then a Tails persistence partition exists on USB drive "old" 0.432
And I shutdown Tails and wait for the computer to power off 3.992
After features/support/hooks.rb:339 0.614
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.418
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.153
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.216
Then Tails is running from USB drive "old" 0.206
And all tps features are active 7.196
When I write some files expected to persist 1.058
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.216
And all persistent directories from the old Tails version have safe access rights 1.436
And I take note of which tps features are available 5.983
And I shutdown Tails and wait for the computer to power off 2.520
# 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.299
After features/support/hooks.rb:339 0.384
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.980
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 7.849
And I log in to a new session 11.621
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.717
And I plug USB drive "to_upgrade" 2.224
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.811
Then the running Tails is installed on USB drive "to_upgrade" 17.477
And I unplug USB drive "to_upgrade" 0.135
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:339 1.763
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.117
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.401
Then all tps features from the old Tails version are active 1.105
And Tails is running from USB drive "to_upgrade" 0.264
And the boot device has safe access rights 2.035
And the expected persistent files created with the old Tails version are present in the filesystem 0.725
And all persistent directories from the old Tails version have safe access rights 1.504
After features/support/hooks.rb:339 0.507
After features/support/hooks.rb:108 0.019
3:18.392
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 7.916
And no SquashFS delta is installed 0.050
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.133
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.160
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.034
And Tor is ready 11.422
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.833
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.407
Given I shutdown Tails and wait for the computer to power off 5.404
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.915
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 7.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.152
And only the 6.2~testoverlayfs SquashFS delta is installed 0.023
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.074
# 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.205
When the network is plugged 0.035
And Tor is ready 10.156
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.840
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.591
Given I shutdown Tails and wait for the computer to power off 2.546
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.146
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.408
And the file system changes introduced in version 6.3~testoverlayfs are present 0.334
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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.178
When the network is plugged 0.022
And Tor is ready 10.071
Then the Upgrader considers the system as up-to-date 0.136
# 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.176
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.294
After features/support/hooks.rb:339 0.937
After features/support/hooks.rb:108 0.019
18.331
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.535
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.169
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.030
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 10.253
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.279
After features/support/hooks.rb:339 0.837
After features/support/hooks.rb:108 0.000