Project Number Date
test_Tails_ISO_devel 4656 04 Oct 2026, 11:17

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:34.943 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.308
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.904
When I start Tails from USB drive "old" with network unplugged 58.352
Then the boot device has safe access rights 2.273
And Tails is running from USB drive "old" 0.192
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.161
After features/support/hooks.rb:339 3.763
After features/support/hooks.rb:108 0.006
Tags: @product
1:26.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 49.643
Then Tails is running from USB drive "old" 0.210
And I create a persistent partition 25.550
And I take note of which tps features are available 6.382
Then a Tails persistence partition exists on USB drive "old" 0.477
And I shutdown Tails and wait for the computer to power off 4.016
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.229
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.107
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.563
Then Tails is running from USB drive "old" 0.176
And all tps features are active 7.802
When I write some files expected to persist 1.188
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.236
And all persistent directories from the old Tails version have safe access rights 1.639
And I take note of which tps features are available 5.844
And I shutdown Tails and wait for the computer to power off 2.587
# 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.926
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.847
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.412
And I log in to a new session 12.480
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.682
And I plug USB drive "to_upgrade" 2.198
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.250
Then the running Tails is installed on USB drive "to_upgrade" 18.527
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:339 1.822
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.207
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given a computer 0.093
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.470
Then all tps features from the old Tails version are active 1.224
And Tails is running from USB drive "to_upgrade" 0.292
And the boot device has safe access rights 2.282
And the expected persistent files created with the old Tails version are present in the filesystem 1.177
And all persistent directories from the old Tails version have safe access rights 1.666
After features/support/hooks.rb:339 0.590
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:35.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 with a persistent partition enabled and logged in 8.670
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.333
When the network is plugged 0.027
And Tor is ready 11.901
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.899
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.106
Given I shutdown Tails and wait for the computer to power off 6.841
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.426
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.353
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.211
When the network is plugged 0.031
And Tor is ready 10.456
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.972
Given I shutdown Tails and wait for the computer to power off 3.878
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.812
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.551
And the file system changes introduced in version 6.3~testoverlayfs are present 0.320
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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.025
And Tor is ready 10.342
Then the Upgrader considers the system as up-to-date 0.135
# 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.527
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.363
After features/support/hooks.rb:339 0.922
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
19.016
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.004
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.092
But a current signing key is available on our website 0.000
When the network is plugged 0.048
And Tor is ready 10.246
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.313
After features/support/hooks.rb:339 0.708
After features/support/hooks.rb:108 0.000