Project Number Date
test_Tails_ISO_stable 6372 13 May 2026, 02:15

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:29.682 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:3.276
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.383
When I start Tails from USB drive "old" with network unplugged 45.675
Then the boot device has safe access rights 2.490
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.179
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:335 1.264
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.527
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.125
And I start Tails from USB drive "old" with network unplugged and I login 55.962
Then Tails is running from USB drive "old" 0.287
And I create a persistent partition 25.005
And I take note of which tps features are available 0.343
Then a Tails persistence partition exists on USB drive "old" 0.564
And I shutdown Tails and wait for the computer to power off 8.237
After features/support/hooks.rb:335 0.325
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.729
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.327
Then Tails is running from USB drive "old" 0.280
And all tps features are active 1.131
When I write some files expected to persist 1.307
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 2.041
And I take note of which tps features are available 0.167
And I shutdown Tails and wait for the computer to power off 8.608
# 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.326
After features/support/hooks.rb:335 0.104
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.311
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.849
And I log in to a new session 12.974
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.849
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.961
Then the running Tails is installed on USB drive "to_upgrade" 16.095
And I unplug USB drive "to_upgrade" 0.169
And I unplug USB drive "__internal" 0.171
After features/support/hooks.rb:335 2.648
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.609
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.629
Then all tps features from the old Tails version are active 1.080
And Tails is running from USB drive "to_upgrade" 0.240
And the boot device has safe access rights 2.918
And the expected persistent files created with the old Tails version are present in the filesystem 1.180
And all persistent directories from the old Tails version have safe access rights 2.494
After features/support/hooks.rb:335 0.682
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:41.960
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.618
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.265
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.258
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.348
When the network is plugged 0.018
And Tor is ready 13.876
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.753
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.468
Given I shutdown Tails and wait for the computer to power off 10.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.866
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.167
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.215
When the network is plugged 0.014
And Tor is ready 11.951
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.998
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.637
Given I shutdown Tails and wait for the computer to power off 4.051
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.495
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.165
And the file system changes introduced in version 6.3~testoverlayfs are present 0.339
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.166
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.015
And Tor is ready 10.137
Then the Upgrader considers the system as up-to-date 10.663
# 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.404
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:335 1.018
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
21.267
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.754
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 9.606
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.566
After features/support/hooks.rb:335 0.969
After features/support/hooks.rb:104 0.000