Project Number Date
test_Tails_ISO_devel 4061 08 Nov 2025, 12:03

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 16:5.016 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.121
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.380
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 32.297
When I start Tails from USB drive "old" with network unplugged 1:12.581
Then the boot device has safe access rights 2.951
And Tails is running from USB drive "old" 0.319
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.178
After features/support/hooks.rb:331 3.712
After features/support/hooks.rb:100 0.011
Tags: @product
2:2.869
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:23.525
Then Tails is running from USB drive "old" 0.309
And I create a persistent partition 29.208
And I take note of which tps features are available 1.119
Then a Tails persistence partition exists on USB drive "old" 0.741
And I shutdown Tails and wait for the computer to power off 7.802
After features/support/hooks.rb:331 0.573
After features/support/hooks.rb:100 0.008
Tags: @product
2:7.421
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:34.435
Then Tails is running from USB drive "old" 0.466
And all tps features are active 2.016
When I write some files expected to persist 1.638
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.181
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.325
And I take note of which tps features are available 0.490
And I shutdown Tails and wait for the computer to power off 7.457
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.851
After features/support/hooks.rb:331 0.595
After features/support/hooks.rb:100 0.009
Tags: @product
2:31.159
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 11.158
And I log in to a new session 15.253
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.595
And I plug USB drive "to_upgrade" 2.555
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.202
Then the running Tails is installed on USB drive "to_upgrade" 20.016
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.190
After features/support/hooks.rb:331 3.826
After features/support/hooks.rb:100 0.000
Tags: @product
1:43.745
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.169
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:35.539
Then all tps features from the old Tails version are active 1.462
And Tails is running from USB drive "to_upgrade" 0.336
And the boot device has safe access rights 2.884
And the expected persistent files created with the old Tails version are present in the filesystem 1.246
And all persistent directories from the old Tails version have safe access rights 2.107
After features/support/hooks.rb:331 0.567
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
4:57.346
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 12.829
And no SquashFS delta is installed 0.119
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.304
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.231
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.541
When the network is plugged 0.066
And Tor is ready 13.813
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.811
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.684
Given I shutdown Tails and wait for the computer to power off 10.851
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:41.673
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.321
And the file system changes introduced in version 6.2~testoverlayfs are present 0.283
And only the 6.2~testoverlayfs SquashFS delta is installed 0.083
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.203
# 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.265
When the network is plugged 0.069
And Tor is ready 11.639
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.683
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.452
Given I shutdown Tails and wait for the computer to power off 7.753
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:36.065
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.168
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.167
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.054
And Tor is ready 12.174
Then the Upgrader considers the system as up-to-date 0.256
# 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.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.519
After features/support/hooks.rb:331 0.838
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
52.351
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 10.231
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
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.066
And Tor is ready 41.003
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.613
After features/support/hooks.rb:331 0.966
After features/support/hooks.rb:100 0.000