Project Number Date
test_Tails_ISO_devel 4366 29 Apr 2026, 12:48

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 13:43.444 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:6.406
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 15.908
When I start Tails from USB drive "old" with network unplugged 45.583
Then the boot device has safe access rights 2.974
And Tails is running from USB drive "old" 0.242
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.235
After features/support/hooks.rb:331 3.838
After features/support/hooks.rb:100 0.009
Tags: @product
1:38.032
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login 1:1.607
Then Tails is running from USB drive "old" 0.512
And I create a persistent partition 25.877
And I take note of which tps features are available 0.858
Then a Tails persistence partition exists on USB drive "old" 0.638
And I shutdown Tails and wait for the computer to power off 8.464
After features/support/hooks.rb:331 0.406
After features/support/hooks.rb:100 0.008
Tags: @product
1:34.306
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:10.015
Then Tails is running from USB drive "old" 0.258
And all tps features are active 1.333
When I write some files expected to persist 1.424
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.210
And all persistence configuration files have safe access rights 0.510
And all persistent directories from the old Tails version have safe access rights 2.024
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 4.297
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.990
After features/support/hooks.rb:331 0.539
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.201
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.279
And I log in to a new session 16.961
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.884
And I plug USB drive "to_upgrade" 2.387
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.270
Then the running Tails is installed on USB drive "to_upgrade" 17.121
And I unplug USB drive "to_upgrade" 0.157
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.865
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.922
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.304
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.256
And the boot device has safe access rights 2.950
And the expected persistent files created with the old Tails version are present in the filesystem 1.229
And all persistent directories from the old Tails version have safe access rights 2.046
After features/support/hooks.rb:331 0.882
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:14.867
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.104
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.463
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.270
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.494
When the network is plugged 0.029
And Tor is ready 23.594
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.545
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.163
Given I shutdown Tails and wait for the computer to power off 14.731
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.778
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.287
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
And only the 6.2~testoverlayfs SquashFS delta is installed 0.043
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.159
# 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.199
When the network is plugged 0.019
And Tor is ready 42.241
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.695
Given I shutdown Tails and wait for the computer to power off 17.538
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.491
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.771
And the file system changes introduced in version 6.3~testoverlayfs are present 0.636
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.129
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.228
When the network is plugged 0.017
And Tor is ready 21.613
Then the Upgrader considers the system as up-to-date 0.133
# 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.160
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.425
After features/support/hooks.rb:331 0.891
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
30.707
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.702
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.353
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 21.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.581
After features/support/hooks.rb:331 1.066
After features/support/hooks.rb:100 0.000