Project Number Date
test_Tails_ISO_devel 4158 08 Jan 2026, 12:22

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 13:39.828 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:24.342
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.195
And I create a 7200 MiB disk named "old" 0.068
And I plug USB drive "old" 1.039
And I write an old version of the Tails USB image to disk "old" 30.855
When I start Tails from USB drive "old" with network unplugged 48.149
Then the boot device has safe access rights 3.152
And Tails is running from USB drive "old" 0.309
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.274
And I unplug USB drive "old" 0.193
After features/support/hooks.rb:331 3.954
After features/support/hooks.rb:100 0.009
Tags: @product
1:40.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.156
And I start Tails from USB drive "old" with network unplugged and I login 1:1.675
Then Tails is running from USB drive "old" 0.284
And I create a persistent partition 29.074
And I take note of which tps features are available 1.178
Then a Tails persistence partition exists on USB drive "old" 0.667
And I shutdown Tails and wait for the computer to power off 7.574
After features/support/hooks.rb:331 0.351
After features/support/hooks.rb:100 0.011
Tags: @product
1:43.739
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.282
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.888
When I write some files expected to persist 1.468
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.399
And all persistent directories from the old Tails version have safe access rights 2.129
And I take note of which tps features are available 0.410
And I shutdown Tails and wait for the computer to power off 7.712
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.773
After features/support/hooks.rb:331 0.201
After features/support/hooks.rb:100 0.008
Tags: @product
2:32.411
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.447
And I log in to a new session 15.609
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.357
And I plug USB drive "to_upgrade" 2.471
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:41.070
Then the running Tails is installed on USB drive "to_upgrade" 20.055
And I unplug USB drive "to_upgrade" 0.203
And I unplug USB drive "__internal" 0.195
After features/support/hooks.rb:331 3.883
After features/support/hooks.rb:100 0.000
Tags: @product
1:27.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.205
Then all tps features from the old Tails version are active 1.440
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 2.977
And the expected persistent files created with the old Tails version are present in the filesystem 1.221
And all persistent directories from the old Tails version have safe access rights 2.708
After features/support/hooks.rb:331 1.119
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
4:22.290
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.593
And no SquashFS delta is installed 0.076
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.283
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.427
When the network is plugged 0.056
And Tor is ready 13.949
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.725
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.466
Given I shutdown Tails and wait for the computer to power off 11.343
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:22.484
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.044
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.327
When the network is plugged 0.082
And Tor is ready 12.586
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.696
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.256
Given I shutdown Tails and wait for the computer to power off 7.935
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.993
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.069
And the file system changes introduced in version 6.3~testoverlayfs are present 0.638
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.165
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.073
And Tor is ready 12.295
Then the Upgrader considers the system as up-to-date 0.161
# 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 7.878
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.529
After features/support/hooks.rb:331 1.181
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
29.399
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.292
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.398
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.060
And Tor is ready 14.988
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.555
After features/support/hooks.rb:331 0.981
After features/support/hooks.rb:100 0.000