Project Number Date
test_Tails_ISO_stable 6375 14 May 2026, 20:00

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:9.951 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:17.717
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.064
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.395
When I start Tails from USB drive "old" with network unplugged 58.318
Then the boot device has safe access rights 3.172
And Tails is running from USB drive "old" 0.219
And there is no persistence partition on USB drive "old" 0.059
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.218
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:335 3.896
After features/support/hooks.rb:104 0.006
Tags: @product
1:35.255
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 58.089
Then Tails is running from USB drive "old" 0.295
And I create a persistent partition 26.767
And I take note of which tps features are available 0.740
Then a Tails persistence partition exists on USB drive "old" 0.677
And I shutdown Tails and wait for the computer to power off 8.629
After features/support/hooks.rb:335 0.613
After features/support/hooks.rb:104 0.008
Tags: @product
1:27.936
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.692
Then Tails is running from USB drive "old" 0.323
And all tps features are active 1.269
When I write some files expected to persist 1.300
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.148
And all persistence configuration files have safe access rights 0.332
And all persistent directories from the old Tails version have safe access rights 2.322
And I take note of which tps features are available 0.235
And I shutdown Tails and wait for the computer to power off 4.050
# 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.196
After features/support/hooks.rb:335 0.414
After features/support/hooks.rb:104 0.007
Tags: @product
2:16.154
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 8.786
And I log in to a new session 14.026
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.884
And I plug USB drive "to_upgrade" 2.315
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.642
Then the running Tails is installed on USB drive "to_upgrade" 17.199
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:335 3.528
After features/support/hooks.rb:104 0.000
Tags: @product
1:17.092
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:9.569
Then all tps features from the old Tails version are active 1.136
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 2.796
And the expected persistent files created with the old Tails version are present in the filesystem 1.208
And all persistent directories from the old Tails version have safe access rights 2.013
After features/support/hooks.rb:335 0.797
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:55.378
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.731
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.342
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.261
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.018
And Tor is ready 13.811
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.404
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.505
Given I shutdown Tails and wait for the computer to power off 6.919
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.928
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.289
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.191
# 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.252
When the network is plugged 0.016
And Tor is ready 11.347
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.205
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.818
Given I shutdown Tails and wait for the computer to power off 8.411
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.741
Then Tails is running version 6.3~testoverlayfs 0.015
And all tps features are active 1.635
And the file system changes introduced in version 6.3~testoverlayfs are present 0.450
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.226
When the network is plugged 0.018
And Tor is ready 10.448
Then the Upgrader considers the system as up-to-date 10.643
# 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.342
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.333
After features/support/hooks.rb:335 1.140
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
20.416
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.753
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.094
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.345
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.814
After features/support/hooks.rb:335 0.815
After features/support/hooks.rb:104 0.000