Project Number Date
test_Tails_ISO_devel 4199 30 Jan 2026, 11:23

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 12:0.573 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:6.712
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.067
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.877
When I start Tails from USB drive "old" with network unplugged 48.190
Then the boot device has safe access rights 2.837
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 3.427
After features/support/hooks.rb:100 0.006
Tags: @product
1:30.048
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login 54.302
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 26.072
And I take note of which tps features are available 0.768
Then a Tails persistence partition exists on USB drive "old" 0.529
And I shutdown Tails and wait for the computer to power off 8.033
After features/support/hooks.rb:331 0.301
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.465
Then Tails is running from USB drive "old" 0.235
And all tps features are active 1.308
When I write some files expected to persist 1.269
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.860
And I take note of which tps features are available 0.193
And I shutdown Tails and wait for the computer to power off 7.995
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.358
After features/support/hooks.rb:331 0.193
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.980
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.217
And I log in to a new session 10.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.813
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.156
Then the running Tails is installed on USB drive "to_upgrade" 15.937
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:331 2.086
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.794
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.546
Then all tps features from the old Tails version are active 0.937
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 2.683
And the expected persistent files created with the old Tails version are present in the filesystem 1.231
And all persistent directories from the old Tails version have safe access rights 2.072
After features/support/hooks.rb:331 1.166
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
4:12.757
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.496
And no SquashFS delta is installed 0.194
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.187
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.207
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.014
And Tor is ready 13.791
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.239
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.152
Given I shutdown Tails and wait for the computer to power off 9.777
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.367
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.359
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.143
# 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.208
When the network is plugged 0.016
And Tor is ready 40.291
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.441
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.934
Given I shutdown Tails and wait for the computer to power off 8.190
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.081
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.193
And the file system changes introduced in version 6.3~testoverlayfs are present 0.363
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.155
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.240
When the network is plugged 0.021
And Tor is ready 10.851
Then the Upgrader considers the system as up-to-date 10.482
# 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.194
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:331 0.702
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
20.111
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.585
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 10.314
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.764
After features/support/hooks.rb:331 0.751
After features/support/hooks.rb:100 0.000