Project Number Date
test_Tails_ISO_devel 4263 03 Mar 2026, 12:02

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:39.345 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
58.209
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.448
When I start Tails from USB drive "old" with network unplugged 40.384
Then the boot device has safe access rights 2.576
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.130
After features/support/hooks.rb:331 3.905
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.224
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.054
And I start Tails from USB drive "old" with network unplugged and I login 51.048
Then Tails is running from USB drive "old" 0.283
And I create a persistent partition 23.713
And I take note of which tps features are available 0.719
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 7.857
After features/support/hooks.rb:331 0.569
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.408
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.647
Then Tails is running from USB drive "old" 0.225
And all tps features are active 1.022
When I write some files expected to persist 1.193
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.387
And all persistent directories from the old Tails version have safe access rights 1.818
And I take note of which tps features are available 0.150
And I shutdown Tails and wait for the computer to power off 7.900
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.821
After features/support/hooks.rb:331 0.418
After features/support/hooks.rb:100 0.007
Tags: @product
2:19.012
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 without a persistent partition and stopped at Tails Greeter's login screen 8.077
And I log in to a new session 12.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.742
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.513
Then the running Tails is installed on USB drive "to_upgrade" 15.792
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 3.222
After features/support/hooks.rb:100 0.000
Tags: @product
1:13.339
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.957
Then all tps features from the old Tails version are active 0.882
And Tails is running from USB drive "to_upgrade" 0.218
And the boot device has safe access rights 2.492
And the expected persistent files created with the old Tails version are present in the filesystem 1.026
And all persistent directories from the old Tails version have safe access rights 1.713
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
4:53.829
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 8.878
And no SquashFS delta is installed 0.068
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.311
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.320
When the network is plugged 0.043
And Tor is ready 29.805
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.353
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.208
Given I shutdown Tails and wait for the computer to power off 32.361
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.362
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.098
And the file system changes introduced in version 6.2~testoverlayfs are present 0.193
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.175
When the network is plugged 0.017
And Tor is ready 21.500
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.377
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.760
Given I shutdown Tails and wait for the computer to power off 18.531
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.506
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.113
And the file system changes introduced in version 6.3~testoverlayfs are present 0.336
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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.197
When the network is plugged 0.020
And Tor is ready 21.355
Then the Upgrader considers the system as up-to-date 0.099
# 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 3.768
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:331 0.869
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
27.321
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.542
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 19.079
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.387
After features/support/hooks.rb:331 0.886
After features/support/hooks.rb:100 0.000