Project Number Date
test_Tails_ISO_devel 4677 16 Oct 2026, 11:09

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 10:32.786 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
56.507
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.094
When I start Tails from USB drive "old" with network unplugged 39.770
Then the boot device has safe access rights 1.905
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.144
And I unplug USB drive "old" 0.113
After features/support/hooks.rb:339 3.563
After features/support/hooks.rb:108 0.016
Tags: @product
1:18.987
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login 47.400
Then Tails is running from USB drive "old" 0.179
And I create a persistent partition 22.088
And I take note of which tps features are available 6.248
Then a Tails persistence partition exists on USB drive "old" 0.451
And I shutdown Tails and wait for the computer to power off 2.546
After features/support/hooks.rb:339 0.329
After features/support/hooks.rb:108 0.005
Tags: @product
1:26.271
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.676
Then Tails is running from USB drive "old" 0.171
And all tps features are active 6.459
When I write some files expected to persist 0.933
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.114
And all persistence configuration files have safe access rights 0.302
And all persistent directories from the old Tails version have safe access rights 1.436
And I take note of which tps features are available 6.268
And I shutdown Tails and wait for the computer to power off 2.567
# 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.258
After features/support/hooks.rb:339 0.525
After features/support/hooks.rb:108 0.005
Tags: @product
2:11.949
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 without a persistent partition and stopped at Tails Greeter's login screen 8.282
And I log in to a new session 12.436
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.630
And I plug USB drive "to_upgrade" 2.287
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.754
Then the running Tails is installed on USB drive "to_upgrade" 17.319
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.116
After features/support/hooks.rb:339 1.667
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.389
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.070
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.758
Then all tps features from the old Tails version are active 1.024
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 1.806
And the expected persistent files created with the old Tails version are present in the filesystem 0.958
And all persistent directories from the old Tails version have safe access rights 1.541
After features/support/hooks.rb:339 0.810
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:15.079
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 7.945
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.146
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.298
When the network is plugged 0.032
And Tor is ready 12.880
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.315
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.363
Given I shutdown Tails and wait for the computer to power off 5.334
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.242
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 6.917
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
And only the 6.2~testoverlayfs SquashFS delta is installed 0.037
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.076
# 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.161
When the network is plugged 0.033
And Tor is ready 10.099
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.293
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.581
Given I shutdown Tails and wait for the computer to power off 2.549
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.087
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 7.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.286
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.027
And Tor is ready 10.036
Then the Upgrader considers the system as up-to-date 0.081
# 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.024
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.304
After features/support/hooks.rb:339 0.747
After features/support/hooks.rb:108 0.009
Tags: @product @automatic_upgrade
19.602
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 7.711
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.034
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 9.638
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.915
After features/support/hooks.rb:339 0.522
After features/support/hooks.rb:108 0.000