Project Number Date
test_Tails_ISO_devel 4074 15 Nov 2025, 10:00

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:54.354 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
2:11.210
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.231
And I create a 7200 MiB disk named "old" 0.055
And I plug USB drive "old" 1.058
And I write an old version of the Tails USB image to disk "old" 32.934
When I start Tails from USB drive "old" with network unplugged 1:32.471
Then the boot device has safe access rights 3.516
And Tails is running from USB drive "old" 0.298
And there is no persistence partition on USB drive "old" 0.093
And process "udev-watchdog" is running 0.071
And udev-watchdog is monitoring the correct device 0.260
And I unplug USB drive "old" 0.217
After features/support/hooks.rb:331 3.765
After features/support/hooks.rb:100 0.011
Tags: @product
2:11.714
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.202
And I start Tails from USB drive "old" with network unplugged and I login 1:29.795
Then Tails is running from USB drive "old" 0.281
And I create a persistent partition 31.171
And I take note of which tps features are available 1.323
Then a Tails persistence partition exists on USB drive "old" 0.859
And I shutdown Tails and wait for the computer to power off 8.080
After features/support/hooks.rb:331 0.478
After features/support/hooks.rb:100 0.010
Tags: @product
2:18.589
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.173
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:42.832
Then Tails is running from USB drive "old" 0.355
And all tps features are active 2.741
When I write some files expected to persist 1.800
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.235
And all persistence configuration files have safe access rights 0.484
And all persistent directories from the old Tails version have safe access rights 2.566
And I take note of which tps features are available 0.550
And I shutdown Tails and wait for the computer to power off 7.798
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.051
After features/support/hooks.rb:331 0.414
After features/support/hooks.rb:100 0.011
Tags: @product
2:42.924
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 13.677
And I log in to a new session 16.853
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.779
And I plug USB drive "to_upgrade" 2.598
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.398
Then the running Tails is installed on USB drive "to_upgrade" 22.179
And I unplug USB drive "to_upgrade" 0.228
And I unplug USB drive "__internal" 0.209
After features/support/hooks.rb:331 4.251
After features/support/hooks.rb:100 0.000
Tags: @product
1:52.153
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.258
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:41.888
Then all tps features from the old Tails version are active 1.797
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 3.741
And the expected persistent files created with the old Tails version are present in the filesystem 1.671
And all persistent directories from the old Tails version have safe access rights 2.476
After features/support/hooks.rb:331 0.810
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:10.842
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 14.596
And no SquashFS delta is installed 0.107
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.279
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.288
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.564
When the network is plugged 0.058
And Tor is ready 14.434
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.025
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.466
Given I shutdown Tails and wait for the computer to power off 9.574
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:45.653
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.502
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.227
# 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.252
When the network is plugged 0.163
And Tor is ready 12.768
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.688
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.928
Given I shutdown Tails and wait for the computer to power off 7.785
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:42.535
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.502
And the file system changes introduced in version 6.3~testoverlayfs are present 0.488
And only the 6.3~testoverlayfs SquashFS delta is installed 0.056
# 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.151
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.276
When the network is plugged 0.057
And Tor is ready 12.422
Then the Upgrader considers the system as up-to-date 0.234
# 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 6.602
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.729
After features/support/hooks.rb:331 0.983
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
26.919
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.624
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.062
But a current signing key is available on our website 0.000
When the network is plugged 0.067
And Tor is ready 13.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.700
After features/support/hooks.rb:331 1.006
After features/support/hooks.rb:100 0.000