Project Number Date
test_Tails_ISO_web-release-7.12 4 02 Sep 2026, 18:27

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:17.200 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:25.170
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.336
When I start Tails from USB drive "old" with network unplugged 1:6.517
Then the boot device has safe access rights 2.493
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.065
And process "udev-watchdog" is running 0.064
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 3.634
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.868
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 53.140
Then Tails is running from USB drive "old" 0.205
And I create a persistent partition 25.680
And I take note of which tps features are available 7.071
Then a Tails persistence partition exists on USB drive "old" 0.531
And I shutdown Tails and wait for the computer to power off 4.154
After features/support/hooks.rb:339 0.502
After features/support/hooks.rb:108 0.006
Tags: @product
1:39.969
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.754
Then Tails is running from USB drive "old" 0.264
And all tps features are active 9.994
When I write some files expected to persist 1.166
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.173
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 2.044
And I take note of which tps features are available 6.442
And I shutdown Tails and wait for the computer to power off 4.046
# 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" 11.665
After features/support/hooks.rb:339 0.372
After features/support/hooks.rb:108 0.007
Tags: @product
2:16.798
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 8.455
And I log in to a new session 13.057
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.927
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.879
Then the running Tails is installed on USB drive "to_upgrade" 20.002
And I unplug USB drive "to_upgrade" 0.117
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 2.251
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.881
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.441
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.021
Then all tps features from the old Tails version are active 1.155
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.717
And the expected persistent files created with the old Tails version are present in the filesystem 1.280
And all persistent directories from the old Tails version have safe access rights 2.060
After features/support/hooks.rb:339 0.963
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:51.922
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.267
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.242
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.197
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.321
When the network is plugged 0.033
And Tor is ready 13.231
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.265
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.727
Given I shutdown Tails and wait for the computer to power off 5.425
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.036
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 11.487
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.138
# 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.249
When the network is plugged 0.057
And Tor is ready 10.344
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.363
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.811
Given I shutdown Tails and wait for the computer to power off 4.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.789
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.477
And the file system changes introduced in version 6.3~testoverlayfs are present 0.401
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.101
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.037
And Tor is ready 10.393
Then the Upgrader considers the system as up-to-date 0.086
# 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 3.249
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:339 0.990
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
20.590
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.297
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.302
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.087
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 9.854
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.957
After features/support/hooks.rb:339 0.618
After features/support/hooks.rb:108 0.000