Project Number Date
test_Tails_ISO_stable 6225 23 Mar 2026, 20:11

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 14:25.051 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:50.373
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.922
When I start Tails from USB drive "old" with network unplugged 1:30.391
Then the boot device has safe access rights 3.204
And Tails is running from USB drive "old" 0.256
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 1.485
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.382
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 "old" with network unplugged and I login 59.442
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 25.032
And I take note of which tps features are available 0.977
Then a Tails persistence partition exists on USB drive "old" 0.587
And I shutdown Tails and wait for the computer to power off 7.028
After features/support/hooks.rb:331 0.604
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.505
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.479
Then Tails is running from USB drive "old" 0.257
And all tps features are active 1.214
When I write some files expected to persist 1.428
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.450
And all persistent directories from the old Tails version have safe access rights 2.007
And I take note of which tps features are available 0.165
And I shutdown Tails and wait for the computer to power off 8.250
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.018
After features/support/hooks.rb:331 0.337
After features/support/hooks.rb:100 0.006
Tags: @product
2:26.631
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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.943
And I log in to a new session 23.239
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.018
And I plug USB drive "to_upgrade" 2.367
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.675
Then the running Tails is installed on USB drive "to_upgrade" 17.946
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.266
After features/support/hooks.rb:331 3.428
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.856
Then all tps features from the old Tails version are active 1.015
And Tails is running from USB drive "to_upgrade" 0.278
And the boot device has safe access rights 2.927
And the expected persistent files created with the old Tails version are present in the filesystem 1.298
And all persistent directories from the old Tails version have safe access rights 3.490
After features/support/hooks.rb:331 0.939
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:16.867
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.643
And no SquashFS delta is installed 0.068
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.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.315
When the network is plugged 0.024
And Tor is ready 24.129
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.470
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.950
Given I shutdown Tails and wait for the computer to power off 19.592
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.110
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.362
And the file system changes introduced in version 6.2~testoverlayfs are present 0.255
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.170
# 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.236
When the network is plugged 0.017
And Tor is ready 41.340
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.382
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.933
Given I shutdown Tails and wait for the computer to power off 18.044
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.312
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.258
And the file system changes introduced in version 6.3~testoverlayfs are present 0.435
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.023
And Tor is ready 22.690
Then the Upgrader considers the system as up-to-date 0.125
# 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.539
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.422
After features/support/hooks.rb:331 0.928
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
30.344
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.375
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.346
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 21.073
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.426
After features/support/hooks.rb:331 0.881
After features/support/hooks.rb:100 0.000