Project Number Date
test_Tails_ISO_devel 4584 02 Sep 2026, 07:30

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:58.343 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.829
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.996
When I start Tails from USB drive "old" with network unplugged 49.430
Then the boot device has safe access rights 1.814
And Tails is running from USB drive "old" 0.163
And there is no persistence partition on USB drive "old" 0.030
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.115
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:339 3.687
After features/support/hooks.rb:108 0.011
Tags: @product
1:19.052
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.208
Then Tails is running from USB drive "old" 0.186
And I create a persistent partition 22.121
And I take note of which tps features are available 6.002
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 3.959
After features/support/hooks.rb:339 0.249
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.903
Then Tails is running from USB drive "old" 0.214
And all tps features are active 7.114
When I write some files expected to persist 0.977
# 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.254
And all persistent directories from the old Tails version have safe access rights 1.488
And I take note of which tps features are available 5.741
And I shutdown Tails and wait for the computer to power off 2.497
# 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.173
After features/support/hooks.rb:339 0.182
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.625
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.212
And I log in to a new session 10.802
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.592
And I plug USB drive "to_upgrade" 2.190
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.058
Then the running Tails is installed on USB drive "to_upgrade" 17.531
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.117
After features/support/hooks.rb:339 1.436
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.714
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.900
Then all tps features from the old Tails version are active 1.089
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.050
And the expected persistent files created with the old Tails version are present in the filesystem 0.800
And all persistent directories from the old Tails version have safe access rights 1.540
After features/support/hooks.rb:339 0.520
After features/support/hooks.rb:108 0.005
3:30.312
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.037
And no SquashFS delta is installed 0.096
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.031
And Tor is ready 13.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.894
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.494
Given I shutdown Tails and wait for the computer to power off 5.239
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.271
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.926
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.034
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.079
# 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.169
When the network is plugged 0.033
And Tor is ready 10.153
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.855
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.628
Given I shutdown Tails and wait for the computer to power off 2.603
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.074
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 7.115
And the file system changes introduced in version 6.3~testoverlayfs are present 0.300
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.075
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.031
And Tor is ready 9.944
Then the Upgrader considers the system as up-to-date 10.438
# 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.049
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.626
After features/support/hooks.rb:108 0.010
19.189
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.799
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
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.037
And Tor is ready 10.233
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.832
After features/support/hooks.rb:339 0.956
After features/support/hooks.rb:108 0.000