Project Number Date
test_Tails_ISO_devel 4255 26 Feb 2026, 12: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 14:46.854 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:26.797
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.049
And I write an old version of the Tails USB image to disk "old" 28.245
When I start Tails from USB drive "old" with network unplugged 53.283
Then the boot device has safe access rights 3.168
And Tails is running from USB drive "old" 0.287
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.062
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 4.005
After features/support/hooks.rb:100 0.012
Tags: @product
1:42.483
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.210
And I start Tails from USB drive "old" with network unplugged and I login 1:2.661
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 29.207
And I take note of which tps features are available 1.161
Then a Tails persistence partition exists on USB drive "old" 1.052
And I shutdown Tails and wait for the computer to power off 7.912
After features/support/hooks.rb:331 0.532
After features/support/hooks.rb:100 0.010
Tags: @product
2:0.198
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:22.472
Then Tails is running from USB drive "old" 0.822
And all tps features are active 5.333
When I write some files expected to persist 1.533
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.390
And all persistent directories from the old Tails version have safe access rights 2.269
And I take note of which tps features are available 0.732
And I shutdown Tails and wait for the computer to power off 8.218
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.960
After features/support/hooks.rb:331 0.190
After features/support/hooks.rb:100 0.024
Tags: @product
2:21.059
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 9.951
And I log in to a new session 9.898
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.323
And I plug USB drive "to_upgrade" 2.453
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.898
Then the running Tails is installed on USB drive "to_upgrade" 19.163
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.179
After features/support/hooks.rb:331 1.781
After features/support/hooks.rb:100 0.000
Tags: @product
1:25.995
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.173
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.572
Then all tps features from the old Tails version are active 2.223
And Tails is running from USB drive "to_upgrade" 0.403
And the boot device has safe access rights 3.492
And the expected persistent files created with the old Tails version are present in the filesystem 1.496
And all persistent directories from the old Tails version have safe access rights 2.632
After features/support/hooks.rb:331 0.991
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:15.275
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.335
And no SquashFS delta is installed 0.108
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.438
When the network is plugged 0.072
And Tor is ready 20.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.624
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.094
Given I shutdown Tails and wait for the computer to power off 14.203
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.200
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.495
And the file system changes introduced in version 6.2~testoverlayfs are present 0.465
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.247
When the network is plugged 0.062
And Tor is ready 23.156
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.627
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.947
Given I shutdown Tails and wait for the computer to power off 18.819
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:28.286
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.681
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.410
When the network is plugged 0.091
And Tor is ready 22.947
Then the Upgrader considers the system as up-to-date 0.123
# 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 6.698
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.538
After features/support/hooks.rb:331 2.619
After features/support/hooks.rb:100 0.038
Tags: @product @automatic_upgrade
35.043
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 18.197
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.087
And Tor is ready 15.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.599
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.000