Project Number Date
test_Tails_ISO_devel 4424 01 Jun 2026, 11:04

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:12.102 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:11.377
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.552
When I start Tails from USB drive "old" with network unplugged 53.343
Then the boot device has safe access rights 2.677
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.197
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:335 3.762
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.148
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login 51.886
Then Tails is running from USB drive "old" 0.259
And I create a persistent partition 23.796
And I take note of which tps features are available 0.339
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 8.253
After features/support/hooks.rb:335 0.245
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.209
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.596
Then Tails is running from USB drive "old" 0.225
And all tps features are active 1.087
When I write some files expected to persist 1.221
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.200
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.971
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 8.271
# 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.099
After features/support/hooks.rb:335 0.201
After features/support/hooks.rb:104 0.008
Tags: @product
2:10.004
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 7.940
And I log in to a new session 12.062
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.815
And I plug USB drive "to_upgrade" 2.215
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.203
Then the running Tails is installed on USB drive "to_upgrade" 15.493
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 1.978
After features/support/hooks.rb:104 0.000
Tags: @product
1:5.441
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.982
Then all tps features from the old Tails version are active 0.943
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.248
And the expected persistent files created with the old Tails version are present in the filesystem 1.094
And all persistent directories from the old Tails version have safe access rights 1.864
After features/support/hooks.rb:335 0.826
After features/support/hooks.rb:104 0.008
3:35.374
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.340
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.179
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.375
When the network is plugged 0.016
And Tor is ready 13.185
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.432
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.773
Given I shutdown Tails and wait for the computer to power off 9.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.447
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.207
And the file system changes introduced in version 6.2~testoverlayfs are present 0.228
And only the 6.2~testoverlayfs SquashFS delta is installed 0.077
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.165
# 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.188
When the network is plugged 0.015
And Tor is ready 11.145
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.317
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.805
Given I shutdown Tails and wait for the computer to power off 8.168
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.956
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.155
And the file system changes introduced in version 6.3~testoverlayfs are present 0.332
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.014
And Tor is ready 10.116
Then the Upgrader considers the system as up-to-date 10.511
# 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.726
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.387
After features/support/hooks.rb:335 1.040
After features/support/hooks.rb:104 0.017
20.545
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.418
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.816
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.971
After features/support/hooks.rb:335 0.649
After features/support/hooks.rb:104 0.000