Project Number Date
test_Tails_ISO_stable 6003 11 Dec 2025, 17:18

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:58.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:39.194
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.185
And I create a 7200 MiB disk named "old" 0.050
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 30.957
When I start Tails from USB drive "old" with network unplugged 1:2.415
Then the boot device has safe access rights 3.490
And Tails is running from USB drive "old" 0.395
And there is no persistence partition on USB drive "old" 0.106
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.264
And I unplug USB drive "old" 0.216
After features/support/hooks.rb:331 3.828
After features/support/hooks.rb:100 0.009
Tags: @product
1:44.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:4.893
Then Tails is running from USB drive "old" 0.293
And I create a persistent partition 29.288
And I take note of which tps features are available 1.327
Then a Tails persistence partition exists on USB drive "old" 0.762
And I shutdown Tails and wait for the computer to power off 7.734
After features/support/hooks.rb:331 0.520
After features/support/hooks.rb:100 0.010
Tags: @product
1:47.634
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.164
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:14.522
Then Tails is running from USB drive "old" 0.307
And all tps features are active 2.071
When I write some files expected to persist 1.550
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.329
And all persistent directories from the old Tails version have safe access rights 2.238
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.666
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 18.130
After features/support/hooks.rb:331 0.328
After features/support/hooks.rb:100 0.010
Tags: @product
2:35.444
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.897
And I log in to a new session 17.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.992
And I plug USB drive "to_upgrade" 2.594
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.004
Then the running Tails is installed on USB drive "to_upgrade" 21.441
And I unplug USB drive "to_upgrade" 0.188
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:331 4.053
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.401
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.198
Then all tps features from the old Tails version are active 1.426
And Tails is running from USB drive "to_upgrade" 0.335
And the boot device has safe access rights 2.928
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 2.966
After features/support/hooks.rb:331 1.133
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:22.214
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.064
And no SquashFS delta is installed 0.118
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.083
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.272
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.418
When the network is plugged 0.052
And Tor is ready 13.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.669
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.064
Given I shutdown Tails and wait for the computer to power off 11.579
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:21.673
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.116
And the file system changes introduced in version 6.2~testoverlayfs are present 0.295
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.173
# 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.062
And Tor is ready 12.118
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.805
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.026
Given I shutdown Tails and wait for the computer to power off 8.814
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.536
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.542
And the file system changes introduced in version 6.3~testoverlayfs are present 0.426
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.143
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.224
When the network is plugged 0.075
And Tor is ready 12.058
Then the Upgrader considers the system as up-to-date 0.163
# 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.493
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.482
After features/support/hooks.rb:331 1.096
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
25.151
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.524
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.246
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.063
But a current signing key is available on our website 0.000
When the network is plugged 0.049
And Tor is ready 11.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.843
After features/support/hooks.rb:331 3.563
After features/support/hooks.rb:100 0.000