Project Number Date
test_Tails_ISO_stable 6464 19 Jun 2026, 11:54

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:33.988 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:16.409
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.037
And I write an old version of the Tails USB image to disk "old" 13.965
When I start Tails from USB drive "old" with network unplugged 57.703
Then the boot device has safe access rights 2.800
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.266
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:339 1.655
After features/support/hooks.rb:108 0.023
Tags: @product
1:31.027
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.024
Given a computer 0.168
And I start Tails from USB drive "old" with network unplugged and I login 54.592
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 24.364
And I take note of which tps features are available 4.003
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.039
After features/support/hooks.rb:339 0.358
After features/support/hooks.rb:108 0.019
Tags: @product
1:44.203
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.422
Then Tails is running from USB drive "old" 0.267
And all tps features are active 4.965
When I write some files expected to persist 1.323
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.393
And all persistent directories from the old Tails version have safe access rights 2.246
And I take note of which tps features are available 4.265
And I shutdown Tails and wait for the computer to power off 8.433
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.548
After features/support/hooks.rb:339 0.162
After features/support/hooks.rb:108 0.022
Tags: @product
2:14.903
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.789
And I log in to a new session 14.517
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.885
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.787
Then the running Tails is installed on USB drive "to_upgrade" 16.391
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 2.213
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.560
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.545
Then all tps features from the old Tails version are active 0.974
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.562
And the expected persistent files created with the old Tails version are present in the filesystem 1.213
And all persistent directories from the old Tails version have safe access rights 1.841
After features/support/hooks.rb:339 0.718
After features/support/hooks.rb:108 0.070
Tags: @product @automatic_upgrade
4:11.249
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.022
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.980
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
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.396
When the network is plugged 0.022
And Tor is ready 12.800
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.295
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.787
Given I shutdown Tails and wait for the computer to power off 10.113
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.215
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.690
And the file system changes introduced in version 6.2~testoverlayfs are present 0.484
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.175
# 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.236
When the network is plugged 0.014
And Tor is ready 10.349
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.962
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.621
Given I shutdown Tails and wait for the computer to power off 7.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.978
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 6.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.541
And only the 6.3~testoverlayfs SquashFS delta is installed 0.097
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.015
And Tor is ready 10.270
Then the Upgrader considers the system as up-to-date 10.599
# 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.910
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:339 0.736
After features/support/hooks.rb:108 0.043
Tags: @product @automatic_upgrade
21.635
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.811
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.308
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.098
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 10.472
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.839
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.000