Project Number Date
test_Tails_ISO_devel 4453 16 Jun 2026, 19:53

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 12:2.111 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:1.717
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.187
And I create a 7200 MiB disk named "old" 0.032
And I plug USB drive "old" 1.038
And I write an old version of the Tails USB image to disk "old" 13.764
When I start Tails from USB drive "old" with network unplugged 43.206
Then the boot device has safe access rights 2.757
And Tails is running from USB drive "old" 0.271
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:339 3.957
After features/support/hooks.rb:108 0.023
Tags: @product
1:33.144
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.223
And I start Tails from USB drive "old" with network unplugged and I login 54.887
Then Tails is running from USB drive "old" 0.263
And I create a persistent partition 25.456
And I take note of which tps features are available 4.771
Then a Tails persistence partition exists on USB drive "old" 0.565
And I shutdown Tails and wait for the computer to power off 6.976
After features/support/hooks.rb:339 0.276
After features/support/hooks.rb:108 0.022
Tags: @product
1:36.586
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given a computer 0.149
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.444
Then Tails is running from USB drive "old" 0.256
And all tps features are active 5.405
When I write some files expected to persist 1.338
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 1.932
And I take note of which tps features are available 4.208
And I shutdown Tails and wait for the computer to power off 2.877
# 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.465
After features/support/hooks.rb:339 0.244
After features/support/hooks.rb:108 0.025
Tags: @product
2:12.127
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.250
And I log in to a new session 12.758
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.773
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.686
Then the running Tails is installed on USB drive "to_upgrade" 15.110
And I unplug USB drive "to_upgrade" 0.168
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.283
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.357
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.167
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.931
Then all tps features from the old Tails version are active 1.054
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.502
And the expected persistent files created with the old Tails version are present in the filesystem 1.378
And all persistent directories from the old Tails version have safe access rights 2.083
After features/support/hooks.rb:339 0.925
After features/support/hooks.rb:108 0.043
4:3.692
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.777
And no SquashFS delta is installed 0.097
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.222
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.406
When the network is plugged 0.015
And Tor is ready 12.810
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.047
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.329
Given I shutdown Tails and wait for the computer to power off 10.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.364
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.076
And the file system changes introduced in version 6.2~testoverlayfs are present 0.394
And only the 6.2~testoverlayfs SquashFS delta is installed 0.085
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.248
When the network is plugged 0.021
And Tor is ready 10.209
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.436
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.046
Given I shutdown Tails and wait for the computer to power off 8.852
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.472
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.333
And the file system changes introduced in version 6.3~testoverlayfs are present 0.442
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.147
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.245
When the network is plugged 0.013
And Tor is ready 9.629
Then the Upgrader considers the system as up-to-date 10.613
# 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.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.389
After features/support/hooks.rb:339 0.756
After features/support/hooks.rb:108 0.038
20.485
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.926
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.006
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.161
After features/support/hooks.rb:339 0.779
After features/support/hooks.rb:108 0.000