Project Number Date
test_Tails_ISO_devel 4675 14 Oct 2026, 11:12

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:49.921 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
59.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.088
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" 13.272
When I start Tails from USB drive "old" with network unplugged 42.427
Then the boot device has safe access rights 1.790
And Tails is running from USB drive "old" 0.178
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.149
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.355
After features/support/hooks.rb:108 0.026
Tags: @product
1:20.259
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 46.448
Then Tails is running from USB drive "old" 0.183
And I create a persistent partition 22.897
And I take note of which tps features are available 6.096
Then a Tails persistence partition exists on USB drive "old" 0.499
And I shutdown Tails and wait for the computer to power off 4.060
After features/support/hooks.rb:339 0.572
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.106
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.641
Then Tails is running from USB drive "old" 0.196
And all tps features are active 6.964
When I write some files expected to persist 1.070
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.197
And all persistent directories from the old Tails version have safe access rights 1.660
And I take note of which tps features are available 5.775
And I shutdown Tails and wait for the computer to power off 2.515
# 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.407
After features/support/hooks.rb:339 0.122
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.488
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.060
And I log in to a new session 11.824
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.687
And I plug USB drive "to_upgrade" 2.174
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.256
Then the running Tails is installed on USB drive "to_upgrade" 17.235
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.469
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.279
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 "to_upgrade" with network unplugged and I login with persistence enabled 58.712
Then all tps features from the old Tails version are active 1.001
And Tails is running from USB drive "to_upgrade" 0.181
And the boot device has safe access rights 1.900
And the expected persistent files created with the old Tails version are present in the filesystem 0.875
And all persistent directories from the old Tails version have safe access rights 1.527
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.005
3:28.223
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 21.072
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.184
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.175
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.268
When the network is plugged 0.028
And Tor is ready 11.407
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.407
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.450
Given I shutdown Tails and wait for the computer to power off 5.211
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.795
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.106
And the file system changes introduced in version 6.2~testoverlayfs are present 0.181
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.106
# 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.144
When the network is plugged 0.022
And Tor is ready 10.121
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.576
Given I shutdown Tails and wait for the computer to power off 2.611
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.085
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 7.486
And the file system changes introduced in version 6.3~testoverlayfs are present 0.302
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.124
When the network is plugged 0.035
And Tor is ready 10.247
Then the Upgrader considers the system as up-to-date 0.078
# 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.069
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.320
After features/support/hooks.rb:339 0.492
After features/support/hooks.rb:108 0.009
18.801
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.727
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.831
After features/support/hooks.rb:339 0.858
After features/support/hooks.rb:108 0.000