Project Number Date
test_Tails_ISO_web-release-7.12 3 02 Sep 2026, 18:16

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:53.963 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.461
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 14.603
When I start Tails from USB drive "old" with network unplugged 57.503
Then the boot device has safe access rights 2.582
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 1.205
After features/support/hooks.rb:108 0.007
Tags: @product
1:27.057
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login 52.110
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 23.495
And I take note of which tps features are available 6.282
Then a Tails persistence partition exists on USB drive "old" 0.617
And I shutdown Tails and wait for the computer to power off 4.178
After features/support/hooks.rb:339 0.244
After features/support/hooks.rb:108 0.010
Tags: @product
1:42.215
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.424
Then Tails is running from USB drive "old" 0.229
And all tps features are active 9.592
When I write some files expected to persist 1.180
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.286
And all persistent directories from the old Tails version have safe access rights 1.787
And I take note of which tps features are available 7.539
And I shutdown Tails and wait for the computer to power off 2.718
# 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.090
After features/support/hooks.rb:339 0.109
After features/support/hooks.rb:108 0.006
Tags: @product
2:16.972
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 9.072
And I log in to a new session 13.522
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.895
And I plug USB drive "to_upgrade" 2.303
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.110
Then the running Tails is installed on USB drive "to_upgrade" 18.811
And I unplug USB drive "to_upgrade" 0.130
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 2.079
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.003
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.105
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.336
Then all tps features from the old Tails version are active 1.096
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.310
And the expected persistent files created with the old Tails version are present in the filesystem 1.043
And all persistent directories from the old Tails version have safe access rights 1.883
After features/support/hooks.rb:339 0.763
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:38.959
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.540
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.350
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.333
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.546
When the network is plugged 0.045
And Tor is ready 11.982
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.483
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.970
Given I shutdown Tails and wait for the computer to power off 4.243
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.295
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 9.246
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.204
When the network is plugged 0.023
And Tor is ready 11.648
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.361
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.419
Given I shutdown Tails and wait for the computer to power off 3.946
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.360
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 7.930
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.122
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.039
And Tor is ready 10.557
Then the Upgrader considers the system as up-to-date 0.137
# 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.588
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:339 0.886
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.294
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 8.419
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.033
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.028
And Tor is ready 9.564
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.954
After features/support/hooks.rb:339 0.890
After features/support/hooks.rb:108 0.000