Project Number Date
test_Tails_ISO_devel 4337 12 Apr 2026, 11:05

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:9.478 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:8.839
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.192
When I start Tails from USB drive "old" with network unplugged 49.386
Then the boot device has safe access rights 3.290
And Tails is running from USB drive "old" 0.363
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.187
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:331 1.346
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.738
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 56.742
Then Tails is running from USB drive "old" 0.365
And I create a persistent partition 23.908
And I take note of which tps features are available 0.818
Then a Tails persistence partition exists on USB drive "old" 0.651
And I shutdown Tails and wait for the computer to power off 8.183
After features/support/hooks.rb:331 0.679
After features/support/hooks.rb:100 0.013
Tags: @product
1:32.677
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.022
Given a computer 0.099
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.457
Then Tails is running from USB drive "old" 0.388
And all tps features are active 1.543
When I write some files expected to persist 1.510
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.193
And all persistence configuration files have safe access rights 0.579
And all persistent directories from the old Tails version have safe access rights 2.393
And I take note of which tps features are available 0.189
And I shutdown Tails and wait for the computer to power off 8.323
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.999
After features/support/hooks.rb:331 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:14.404
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.280
And I log in to a new session 13.425
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.780
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.837
Then the running Tails is installed on USB drive "to_upgrade" 17.407
And I unplug USB drive "to_upgrade" 0.274
And I unplug USB drive "__internal" 0.170
After features/support/hooks.rb:331 2.265
After features/support/hooks.rb:100 0.000
Tags: @product
1:21.946
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.133
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.850
Then all tps features from the old Tails version are active 1.256
And Tails is running from USB drive "to_upgrade" 0.847
And the boot device has safe access rights 3.892
And the expected persistent files created with the old Tails version are present in the filesystem 1.322
And all persistent directories from the old Tails version have safe access rights 2.643
After features/support/hooks.rb:331 0.993
After features/support/hooks.rb:100 0.014
Tags: @product @automatic_upgrade
4:53.732
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.039
And no SquashFS delta is installed 0.073
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.216
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
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.409
When the network is plugged 0.021
And Tor is ready 22.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.597
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.141
Given I shutdown Tails and wait for the computer to power off 19.336
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.582
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.213
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.130
# 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.184
When the network is plugged 0.017
And Tor is ready 21.261
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.369
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.177
Given I shutdown Tails and wait for the computer to power off 18.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.050
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.273
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.248
When the network is plugged 0.016
And Tor is ready 22.802
Then the Upgrader considers the system as up-to-date 0.138
# 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.448
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.541
After features/support/hooks.rb:331 0.990
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
27.140
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.016
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.301
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.064
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 18.085
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.372
After features/support/hooks.rb:331 0.648
After features/support/hooks.rb:100 0.000