Project Number Date
test_Tails_ISO_devel 4416 26 May 2026, 21: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 12:8.251 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.052
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.100
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.736
When I start Tails from USB drive "old" with network unplugged 45.341
Then the boot device has safe access rights 2.947
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.055
And udev-watchdog is monitoring the correct device 0.342
And I unplug USB drive "old" 0.182
After features/support/hooks.rb:335 3.680
After features/support/hooks.rb:104 0.055
Tags: @product
1:33.002
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login 57.999
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 25.152
And I take note of which tps features are available 0.415
Then a Tails persistence partition exists on USB drive "old" 0.685
And I shutdown Tails and wait for the computer to power off 8.395
After features/support/hooks.rb:335 0.471
After features/support/hooks.rb:104 0.006
Tags: @product
1:32.375
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.866
Then Tails is running from USB drive "old" 0.368
And all tps features are active 1.561
When I write some files expected to persist 1.743
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.212
And all persistence configuration files have safe access rights 0.415
And all persistent directories from the old Tails version have safe access rights 2.090
And I take note of which tps features are available 0.181
And I shutdown Tails and wait for the computer to power off 4.278
# 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" 13.587
After features/support/hooks.rb:335 0.481
After features/support/hooks.rb:104 0.006
Tags: @product
2:16.377
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 without a persistent partition and stopped at Tails Greeter's login screen 7.634
And I log in to a new session 14.371
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.825
And I plug USB drive "to_upgrade" 2.301
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.819
Then the running Tails is installed on USB drive "to_upgrade" 17.066
And I unplug USB drive "to_upgrade" 0.205
And I unplug USB drive "__internal" 0.152
After features/support/hooks.rb:335 2.772
After features/support/hooks.rb:104 0.000
Tags: @product
1:17.445
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.099
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.221
Then all tps features from the old Tails version are active 1.119
And Tails is running from USB drive "to_upgrade" 0.359
And the boot device has safe access rights 2.933
And the expected persistent files created with the old Tails version are present in the filesystem 1.341
And all persistent directories from the old Tails version have safe access rights 2.370
After features/support/hooks.rb:335 1.073
After features/support/hooks.rb:104 0.009
Tags: @product @automatic_upgrade
4:2.946
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.936
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.275
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.321
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.423
When the network is plugged 0.019
And Tor is ready 14.139
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.608
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.433
Given I shutdown Tails and wait for the computer to power off 10.022
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.399
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.299
And only the 6.2~testoverlayfs SquashFS delta is installed 0.070
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.142
# 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.407
When the network is plugged 0.023
And Tor is ready 11.685
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.953
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.666
Given I shutdown Tails and wait for the computer to power off 8.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.811
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 1.472
And the file system changes introduced in version 6.3~testoverlayfs are present 0.404
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.015
And Tor is ready 11.472
Then the Upgrader considers the system as up-to-date 10.731
# 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 5.165
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.485
After features/support/hooks.rb:335 1.056
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
21.051
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.468
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.401
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.105
And the signing key used by the Upgrader is outdated 0.084
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 11.142
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.828
After features/support/hooks.rb:335 0.711
After features/support/hooks.rb:104 0.000