Project Number Date
test_Tails_ISO_devel 4482 06 Jul 2026, 07:58

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:59.807 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:5.342
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.111
When I start Tails from USB drive "old" with network unplugged 46.410
Then the boot device has safe access rights 2.909
And Tails is running from USB drive "old" 0.274
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.279
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 3.788
After features/support/hooks.rb:108 0.007
Tags: @product
1:32.409
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 54.520
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 24.952
And I take note of which tps features are available 4.127
Then a Tails persistence partition exists on USB drive "old" 0.485
And I shutdown Tails and wait for the computer to power off 8.005
After features/support/hooks.rb:339 0.517
After features/support/hooks.rb:108 0.007
Tags: @product
1:41.264
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.876
Then Tails is running from USB drive "old" 0.315
And all tps features are active 4.884
When I write some files expected to persist 1.268
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.303
And all persistent directories from the old Tails version have safe access rights 1.985
And I take note of which tps features are available 4.492
And I shutdown Tails and wait for the computer to power off 8.191
# 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.727
After features/support/hooks.rb:339 0.559
After features/support/hooks.rb:108 0.007
Tags: @product
2:12.587
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.294
And I log in to a new session 13.119
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.034
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.996
Then the running Tails is installed on USB drive "to_upgrade" 15.563
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 1.956
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.601
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.960
Then all tps features from the old Tails version are active 1.311
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.783
And the expected persistent files created with the old Tails version are present in the filesystem 1.176
And all persistent directories from the old Tails version have safe access rights 2.090
After features/support/hooks.rb:339 0.650
After features/support/hooks.rb:108 0.006
3:53.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.376
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.565
When the network is plugged 0.020
And Tor is ready 13.500
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.696
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.637
Given I shutdown Tails and wait for the computer to power off 9.557
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.599
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 5.615
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.137
# 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.237
When the network is plugged 0.017
And Tor is ready 9.738
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.638
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.839
Given I shutdown Tails and wait for the computer to power off 8.049
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.287
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.269
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.193
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.014
And Tor is ready 11.985
Then the Upgrader considers the system as up-to-date 0.115
# 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.805
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.474
After features/support/hooks.rb:339 0.896
After features/support/hooks.rb:108 0.013
21.584
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 7.571
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.971
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.685
After features/support/hooks.rb:339 0.888
After features/support/hooks.rb:108 0.000