Project Number Date
test_Tails_ISO_stable 6286 11 Apr 2026, 07:21

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:39.969 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
59.160
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.730
When I start Tails from USB drive "old" with network unplugged 40.750
Then the boot device has safe access rights 2.912
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:331 3.422
After features/support/hooks.rb:100 0.006
Tags: @product
1:28.030
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 54.781
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 23.536
And I take note of which tps features are available 0.675
Then a Tails persistence partition exists on USB drive "old" 0.535
And I shutdown Tails and wait for the computer to power off 8.140
After features/support/hooks.rb:331 0.377
After features/support/hooks.rb:100 0.010
Tags: @product
1:28.604
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.239
Then Tails is running from USB drive "old" 0.270
And all tps features are active 1.263
When I write some files expected to persist 1.448
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.260
And all persistence configuration files have safe access rights 0.429
And all persistent directories from the old Tails version have safe access rights 1.956
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 7.987
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.538
After features/support/hooks.rb:331 0.222
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.277
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 without a persistent partition and stopped at Tails Greeter's login screen 7.934
And I log in to a new session 13.180
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.753
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.778
Then the running Tails is installed on USB drive "to_upgrade" 16.013
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.227
After features/support/hooks.rb:331 1.951
After features/support/hooks.rb:100 0.000
Tags: @product
1:10.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.089
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.177
Then all tps features from the old Tails version are active 0.906
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.302
And the expected persistent files created with the old Tails version are present in the filesystem 1.069
And all persistent directories from the old Tails version have safe access rights 1.991
After features/support/hooks.rb:331 0.949
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
4:55.390
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.741
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
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.253
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.014
And Tor is ready 21.920
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.360
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.519
Given I shutdown Tails and wait for the computer to power off 20.599
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.574
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.125
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.192
When the network is plugged 0.016
And Tor is ready 21.799
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.821
Given I shutdown Tails and wait for the computer to power off 18.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.865
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.210
And the file system changes introduced in version 6.3~testoverlayfs are present 0.392
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.017
And Tor is ready 41.284
Then the Upgrader considers the system as up-to-date 0.098
# 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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:331 0.682
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
25.740
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 7.567
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.276
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 17.428
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.360
After features/support/hooks.rb:331 1.241
After features/support/hooks.rb:100 0.000