Project Number Date
test_Tails_ISO_stable 5925 02 Nov 2025, 12:07

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 15:59.891 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:59.838
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.193
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 33.080
When I start Tails from USB drive "old" with network unplugged 1:21.670
Then the boot device has safe access rights 2.954
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.255
And I unplug USB drive "old" 0.181
After features/support/hooks.rb:331 4.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.948
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 1:24.378
Then Tails is running from USB drive "old" 0.349
And I create a persistent partition 30.625
And I take note of which tps features are available 1.226
Then a Tails persistence partition exists on USB drive "old" 0.699
And I shutdown Tails and wait for the computer to power off 7.501
After features/support/hooks.rb:331 0.629
After features/support/hooks.rb:100 0.008
Tags: @product
2:12.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:37.729
Then Tails is running from USB drive "old" 0.373
And all tps features are active 1.857
When I write some files expected to persist 1.624
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.367
And all persistent directories from the old Tails version have safe access rights 2.746
And I take note of which tps features are available 0.456
And I shutdown Tails and wait for the computer to power off 7.596
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.910
After features/support/hooks.rb:331 0.478
After features/support/hooks.rb:100 0.009
Tags: @product
2:36.356
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 15.150
And I log in to a new session 15.747
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.319
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.876
Then the running Tails is installed on USB drive "to_upgrade" 20.474
And I unplug USB drive "to_upgrade" 0.178
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 4.177
After features/support/hooks.rb:100 0.000
Tags: @product
1:49.315
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.157
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:39.011
Then all tps features from the old Tails version are active 3.500
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.897
And the expected persistent files created with the old Tails version are present in the filesystem 1.309
And all persistent directories from the old Tails version have safe access rights 2.170
After features/support/hooks.rb:331 1.090
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:52.599
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.791
And no SquashFS delta is installed 0.074
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.068
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.311
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.449
When the network is plugged 0.050
And Tor is ready 14.273
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.720
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.219
Given I shutdown Tails and wait for the computer to power off 8.326
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.852
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.447
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.107
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.171
# 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.237
When the network is plugged 0.058
And Tor is ready 12.812
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.587
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.810
Given I shutdown Tails and wait for the computer to power off 4.888
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:38.681
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.316
And the file system changes introduced in version 6.3~testoverlayfs are present 0.430
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.251
When the network is plugged 0.057
And Tor is ready 12.017
Then the Upgrader considers the system as up-to-date 0.190
# 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.135
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.495
After features/support/hooks.rb:331 1.109
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
24.776
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 11.666
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.053
And Tor is ready 10.951
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.730
After features/support/hooks.rb:331 1.117
After features/support/hooks.rb:100 0.000