Project Number Date
test_Tails_ISO_stable 6038 05 Jan 2026, 20:49

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 17:12.984 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
3:39.677
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.052
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 1:24.880
When I start Tails from USB drive "old" with network unplugged 2:9.294
Then the boot device has safe access rights 3.420
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.063
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.223
And I unplug USB drive "old" 0.171
After features/support/hooks.rb:331 3.457
After features/support/hooks.rb:100 0.009
Tags: @product
2:4.555
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.161
And I start Tails from USB drive "old" with network unplugged and I login 1:9.448
Then Tails is running from USB drive "old" 0.737
And I create a persistent partition 41.158
And I take note of which tps features are available 4.273
Then a Tails persistence partition exists on USB drive "old" 0.666
And I shutdown Tails and wait for the computer to power off 8.107
After features/support/hooks.rb:331 0.491
After features/support/hooks.rb:100 0.010
Tags: @product
1:57.020
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:21.234
Then Tails is running from USB drive "old" 1.834
And all tps features are active 4.734
When I write some files expected to persist 1.521
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.190
And all persistence configuration files have safe access rights 0.372
And all persistent directories from the old Tails version have safe access rights 2.252
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 5.009
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.198
After features/support/hooks.rb:331 0.341
After features/support/hooks.rb:100 0.009
Tags: @product
2:58.739
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.024
And I log in to a new session 19.439
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.707
And I plug USB drive "to_upgrade" 2.650
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:57.996
Then the running Tails is installed on USB drive "to_upgrade" 21.515
And I unplug USB drive "to_upgrade" 0.212
And I unplug USB drive "__internal" 0.192
After features/support/hooks.rb:331 4.008
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.400
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.331
Then all tps features from the old Tails version are active 1.757
And Tails is running from USB drive "to_upgrade" 0.386
And the boot device has safe access rights 3.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.479
And all persistent directories from the old Tails version have safe access rights 2.486
After features/support/hooks.rb:331 0.615
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
4:39.736
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.626
And no SquashFS delta is installed 0.178
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.288
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.367
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.559
When the network is plugged 2.911
And Tor is ready 14.545
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.892
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.496
Given I shutdown Tails and wait for the computer to power off 16.182
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:23.970
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 2.195
And the file system changes introduced in version 6.2~testoverlayfs are present 0.328
And only the 6.2~testoverlayfs SquashFS delta is installed 0.086
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.293
When the network is plugged 0.054
And Tor is ready 12.242
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.239
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.637
Given I shutdown Tails and wait for the computer to power off 8.659
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.887
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 4.766
And the file system changes introduced in version 6.3~testoverlayfs are present 0.523
And only the 6.3~testoverlayfs SquashFS delta is installed 0.111
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.274
When the network is plugged 0.048
And Tor is ready 14.031
Then the Upgrader considers the system as up-to-date 0.138
# 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.264
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.520
After features/support/hooks.rb:331 1.108
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
24.854
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.953
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.269
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 11.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.723
After features/support/hooks.rb:331 1.073
After features/support/hooks.rb:100 0.000