Project Number Date
test_Tails_ISO_devel 4413 24 May 2026, 11:08

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:57.657 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:0.924
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.006
When I start Tails from USB drive "old" with network unplugged 43.769
Then the boot device has safe access rights 2.447
And Tails is running from USB drive "old" 0.220
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.124
After features/support/hooks.rb:335 3.666
After features/support/hooks.rb:104 0.018
Tags: @product
1:22.813
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login 52.607
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 24.742
And I take note of which tps features are available 0.342
Then a Tails persistence partition exists on USB drive "old" 0.507
And I shutdown Tails and wait for the computer to power off 4.293
After features/support/hooks.rb:335 0.591
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.592
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.474
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.099
When I write some files expected to persist 1.207
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.811
And I take note of which tps features are available 0.164
And I shutdown Tails and wait for the computer to power off 8.195
# 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.860
After features/support/hooks.rb:335 0.232
After features/support/hooks.rb:104 0.008
Tags: @product
2:9.622
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 8.226
And I log in to a new session 12.472
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.669
And I plug USB drive "to_upgrade" 2.245
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.160
Then the running Tails is installed on USB drive "to_upgrade" 14.548
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:335 2.031
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.637
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.981
Then all tps features from the old Tails version are active 1.061
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.365
And the expected persistent files created with the old Tails version are present in the filesystem 1.066
And all persistent directories from the old Tails version have safe access rights 1.847
After features/support/hooks.rb:335 0.610
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:33.020
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 7.936
And no SquashFS delta is installed 0.076
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.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.205
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.410
When the network is plugged 0.016
And Tor is ready 13.759
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.626
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.442
Given I shutdown Tails and wait for the computer to power off 9.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.320
Then Tails is running version 6.2~testoverlayfs 0.023
And all tps features are active 1.061
And the file system changes introduced in version 6.2~testoverlayfs are present 0.202
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.125
# 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.174
When the network is plugged 0.019
And Tor is ready 9.655
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.042
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.106
Given I shutdown Tails and wait for the computer to power off 7.973
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.633
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.213
And the file system changes introduced in version 6.3~testoverlayfs are present 0.349
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.015
And Tor is ready 9.671
Then the Upgrader considers the system as up-to-date 10.519
# 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.075
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:335 0.837
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.045
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.287
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.197
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.070
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.014
And Tor is ready 9.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.008
After features/support/hooks.rb:335 0.682
After features/support/hooks.rb:104 0.000