Project Number Date
test_Tails_ISO_stable 5931 05 Nov 2025, 08:27

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:50.504 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:54.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.170
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.045
And I write an old version of the Tails USB image to disk "old" 30.360
When I start Tails from USB drive "old" with network unplugged 1:19.229
Then the boot device has safe access rights 2.934
And Tails is running from USB drive "old" 0.276
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.179
After features/support/hooks.rb:331 3.605
After features/support/hooks.rb:100 0.009
Tags: @product
1:59.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.153
And I start Tails from USB drive "old" with network unplugged and I login 1:23.002
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 26.332
And I take note of which tps features are available 1.111
Then a Tails persistence partition exists on USB drive "old" 0.650
And I shutdown Tails and wait for the computer to power off 7.494
After features/support/hooks.rb:331 0.300
After features/support/hooks.rb:100 0.008
Tags: @product
2:2.868
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.174
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:31.027
Then Tails is running from USB drive "old" 0.305
And all tps features are active 1.749
When I write some files expected to persist 1.502
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.199
And all persistence configuration files have safe access rights 0.370
And all persistent directories from the old Tails version have safe access rights 2.117
And I take note of which tps features are available 0.451
And I shutdown Tails and wait for the computer to power off 7.558
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.411
After features/support/hooks.rb:331 0.563
After features/support/hooks.rb:100 0.008
Tags: @product
2:30.358
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 12.315
And I log in to a new session 15.753
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.414
And I plug USB drive "to_upgrade" 2.922
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:38.527
Then the running Tails is installed on USB drive "to_upgrade" 19.013
And I unplug USB drive "to_upgrade" 0.227
And I unplug USB drive "__internal" 0.182
After features/support/hooks.rb:331 4.165
After features/support/hooks.rb:100 0.000
Tags: @product
1:40.961
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.219
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:32.804
Then all tps features from the old Tails version are active 1.316
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.889
And the expected persistent files created with the old Tails version are present in the filesystem 1.240
And all persistent directories from the old Tails version have safe access rights 2.209
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
5:19.731
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.438
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.303
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.053
And Tor is ready 15.107
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.589
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.919
Given I shutdown Tails and wait for the computer to power off 11.071
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:34.820
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 2.025
And the file system changes introduced in version 6.2~testoverlayfs are present 0.294
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.208
# 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.227
When the network is plugged 0.071
And Tor is ready 42.682
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.555
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.713
Given I shutdown Tails and wait for the computer to power off 7.556
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:35.620
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 1.986
And the file system changes introduced in version 6.3~testoverlayfs are present 0.399
And only the 6.3~testoverlayfs SquashFS delta is installed 0.057
# 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.258
When the network is plugged 0.063
And Tor is ready 13.382
Then the Upgrader considers the system as up-to-date 0.194
# 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.670
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.413
After features/support/hooks.rb:331 0.907
After features/support/hooks.rb:100 0.017
Tags: @product @automatic_upgrade
22.938
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 9.933
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.059
But a current signing key is available on our website 0.000
When the network is plugged 0.051
And Tor is ready 10.855
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.718
After features/support/hooks.rb:331 0.938
After features/support/hooks.rb:100 0.000