Project Number Date
test_Tails_ISO_stable 6090 24 Jan 2026, 11:51

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:42.437 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:23.407
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.879
When I start Tails from USB drive "old" with network unplugged 1:5.134
Then the boot device has safe access rights 2.631
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.044
And udev-watchdog is monitoring the correct device 0.189
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:331 3.750
After features/support/hooks.rb:100 0.061
Tags: @product
1:29.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 55.181
Then Tails is running from USB drive "old" 0.244
And I create a persistent partition 25.731
And I take note of which tps features are available 0.659
Then a Tails persistence partition exists on USB drive "old" 0.577
And I shutdown Tails and wait for the computer to power off 7.122
After features/support/hooks.rb:331 0.313
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.206
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 with persistence enabled 1:2.080
Then Tails is running from USB drive "old" 0.264
And all tps features are active 1.106
When I write some files expected to persist 1.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
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.703
And I take note of which tps features are available 0.149
And I shutdown Tails and wait for the computer to power off 8.052
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.188
After features/support/hooks.rb:331 0.154
After features/support/hooks.rb:100 0.007
Tags: @product
2:13.098
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.771
And I log in to a new session 11.163
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.806
And I plug USB drive "to_upgrade" 2.243
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.528
Then the running Tails is installed on USB drive "to_upgrade" 16.217
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.159
After features/support/hooks.rb:331 3.752
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.780
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.300
Then all tps features from the old Tails version are active 0.901
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 2.596
And the expected persistent files created with the old Tails version are present in the filesystem 1.153
And all persistent directories from the old Tails version have safe access rights 2.438
After features/support/hooks.rb:331 1.019
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
3:38.612
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.361
And no SquashFS delta is installed 0.058
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
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.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.015
And Tor is ready 12.641
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.299
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.426
Given I shutdown Tails and wait for the computer to power off 6.811
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.163
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.178
And the file system changes introduced in version 6.2~testoverlayfs are present 0.244
And only the 6.2~testoverlayfs SquashFS delta is installed 0.036
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.235
When the network is plugged 0.014
And Tor is ready 11.178
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.542
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.924
Given I shutdown Tails and wait for the computer to power off 4.446
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.725
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.077
And the file system changes introduced in version 6.3~testoverlayfs are present 0.367
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.015
And Tor is ready 11.756
Then the Upgrader considers the system as up-to-date 10.524
# 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.462
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.599
After features/support/hooks.rb:331 0.840
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
20.764
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.024
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.857
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
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.019
And Tor is ready 9.552
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.993
After features/support/hooks.rb:331 1.024
After features/support/hooks.rb:100 0.000