Project Number Date
test_Tails_ISO_stable 6387 19 May 2026, 18:39

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.640 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:4.358
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 12.977
When I start Tails from USB drive "old" with network unplugged 46.919
Then the boot device has safe access rights 2.623
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.074
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:335 3.736
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.798
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 53.265
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 24.970
And I take note of which tps features are available 0.327
Then a Tails persistence partition exists on USB drive "old" 0.585
And I shutdown Tails and wait for the computer to power off 8.354
After features/support/hooks.rb:335 0.609
After features/support/hooks.rb:104 0.008
Tags: @product
1:19.910
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.968
Then Tails is running from USB drive "old" 0.265
And all tps features are active 1.116
When I write some files expected to persist 1.360
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 1.857
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 2.684
# 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.899
After features/support/hooks.rb:335 0.454
After features/support/hooks.rb:104 0.006
Tags: @product
2:10.773
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.922
And I log in to a new session 13.407
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.735
And I plug USB drive "to_upgrade" 2.276
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.830
Then the running Tails is installed on USB drive "to_upgrade" 14.328
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:335 3.820
After features/support/hooks.rb:104 0.000
Tags: @product
1:8.784
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.476
Then all tps features from the old Tails version are active 0.965
And Tails is running from USB drive "to_upgrade" 0.368
And the boot device has safe access rights 2.770
And the expected persistent files created with the old Tails version are present in the filesystem 1.225
And all persistent directories from the old Tails version have safe access rights 1.918
After features/support/hooks.rb:335 0.949
After features/support/hooks.rb:104 0.011
3:41.394
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.380
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.238
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.396
When the network is plugged 0.016
And Tor is ready 13.505
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.325
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.758
Given I shutdown Tails and wait for the computer to power off 9.499
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.478
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.181
And the file system changes introduced in version 6.2~testoverlayfs are present 0.207
And only the 6.2~testoverlayfs SquashFS delta is installed 0.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.115
# 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.196
When the network is plugged 0.019
And Tor is ready 9.910
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.082
Given I shutdown Tails and wait for the computer to power off 7.912
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.970
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.276
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.063
# 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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.016
And Tor is ready 10.167
Then the Upgrader considers the system as up-to-date 10.566
# 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.158
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.417
After features/support/hooks.rb:335 0.932
After features/support/hooks.rb:104 0.047
19.619
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 with a persistent partition enabled and logged in 7.260
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.390
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.078
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 9.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.017
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.000