Project Number Date
test_Tails_ISO_stable 6724 06 Oct 2026, 07:36

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:2.147 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
56.602
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 13.114
When I start Tails from USB drive "old" with network unplugged 39.588
Then the boot device has safe access rights 2.079
And Tails is running from USB drive "old" 0.293
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.178
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.399
After features/support/hooks.rb:108 0.006
Tags: @product
1:25.200
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 49.847
Then Tails is running from USB drive "old" 0.202
And I create a persistent partition 23.952
And I take note of which tps features are available 6.661
Then a Tails persistence partition exists on USB drive "old" 0.547
And I shutdown Tails and wait for the computer to power off 3.903
After features/support/hooks.rb:339 0.101
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.695
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.211
Then Tails is running from USB drive "old" 0.230
And all tps features are active 7.281
When I write some files expected to persist 1.145
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.220
And all persistence configuration files have safe access rights 0.300
And all persistent directories from the old Tails version have safe access rights 1.856
And I take note of which tps features are available 6.231
And I shutdown Tails and wait for the computer to power off 2.568
# 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.551
After features/support/hooks.rb:339 0.138
After features/support/hooks.rb:108 0.013
Tags: @product
2:13.528
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.626
And I log in to a new session 13.084
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.778
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.563
Then the running Tails is installed on USB drive "to_upgrade" 17.010
And I unplug USB drive "to_upgrade" 0.107
And I unplug USB drive "__internal" 0.125
After features/support/hooks.rb:339 0.906
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.732
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.003
Then all tps features from the old Tails version are active 1.085
And Tails is running from USB drive "to_upgrade" 0.225
And the boot device has safe access rights 2.104
And the expected persistent files created with the old Tails version are present in the filesystem 1.324
And all persistent directories from the old Tails version have safe access rights 1.901
After features/support/hooks.rb:339 0.534
After features/support/hooks.rb:108 0.006
3:31.422
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.390
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.179
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.322
When the network is plugged 0.048
And Tor is ready 13.285
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.403
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.103
Given I shutdown Tails and wait for the computer to power off 5.314
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.927
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 7.546
And the file system changes introduced in version 6.2~testoverlayfs are present 0.157
And only the 6.2~testoverlayfs SquashFS delta is installed 0.060
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.150
# 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.227
When the network is plugged 0.023
And Tor is ready 10.523
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.330
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.796
Given I shutdown Tails and wait for the computer to power off 4.181
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.622
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.338
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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.034
And Tor is ready 10.964
Then the Upgrader considers the system as up-to-date 0.105
# 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.166
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:339 0.995
After features/support/hooks.rb:108 0.059
17.965
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.982
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 8.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.436
After features/support/hooks.rb:339 0.702
After features/support/hooks.rb:108 0.000