Project Number Date
test_Tails_ISO_stable 6228 24 Mar 2026, 12:33

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:44.713 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:34.571
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.077
And I create a 7200 MiB disk named "old" 0.017
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 15.058
When I start Tails from USB drive "old" with network unplugged 1:14.355
Then the boot device has safe access rights 3.139
And Tails is running from USB drive "old" 0.381
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.235
And I unplug USB drive "old" 0.149
After features/support/hooks.rb:331 3.817
After features/support/hooks.rb:100 0.020
Tags: @product
1:33.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 58.616
Then Tails is running from USB drive "old" 0.569
And I create a persistent partition 27.957
And I take note of which tps features are available 0.730
Then a Tails persistence partition exists on USB drive "old" 0.618
And I shutdown Tails and wait for the computer to power off 4.586
After features/support/hooks.rb:331 0.197
After features/support/hooks.rb:100 0.007
Tags: @product
1:33.715
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.973
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.174
When I write some files expected to persist 1.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.179
And all persistence configuration files have safe access rights 0.476
And all persistent directories from the old Tails version have safe access rights 2.248
And I take note of which tps features are available 0.191
And I shutdown Tails and wait for the computer to power off 7.192
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.586
After features/support/hooks.rb:331 0.187
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.491
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 without a persistent partition and stopped at Tails Greeter's login screen 10.185
And I log in to a new session 23.079
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.739
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.969
Then the running Tails is installed on USB drive "to_upgrade" 20.008
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:331 3.942
After features/support/hooks.rb:100 0.000
Tags: @product
1:14.930
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.064
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:6.489
Then all tps features from the old Tails version are active 1.382
And Tails is running from USB drive "to_upgrade" 0.259
And the boot device has safe access rights 3.221
And the expected persistent files created with the old Tails version are present in the filesystem 1.237
And all persistent directories from the old Tails version have safe access rights 2.273
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
4:47.825
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.839
And no SquashFS delta is installed 0.166
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.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.236
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.347
When the network is plugged 0.015
And Tor is ready 26.716
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.396
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.156
Given I shutdown Tails and wait for the computer to power off 14.780
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.454
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 1.278
And the file system changes introduced in version 6.2~testoverlayfs are present 0.293
And only the 6.2~testoverlayfs SquashFS delta is installed 0.104
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.219
# 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.281
When the network is plugged 0.022
And Tor is ready 21.788
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.433
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.629
Given I shutdown Tails and wait for the computer to power off 17.733
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.565
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.380
And the file system changes introduced in version 6.3~testoverlayfs are present 0.467
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.142
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.236
When the network is plugged 0.016
And Tor is ready 22.683
Then the Upgrader considers the system as up-to-date 0.164
# 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.372
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.434
After features/support/hooks.rb:331 0.767
After features/support/hooks.rb:100 0.016
Tags: @product @automatic_upgrade
30.025
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.005
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.334
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.073
And the signing key used by the Upgrader is outdated 0.068
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 21.077
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.430
After features/support/hooks.rb:331 0.943
After features/support/hooks.rb:100 0.000