Project Number Date
test_Tails_ISO_stable 6035 05 Jan 2026, 12:24

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:27.663 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:46.386
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.178
And I create a 7200 MiB disk named "old" 0.047
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 31.759
When I start Tails from USB drive "old" with network unplugged 1:9.581
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.266
And there is no persistence partition on USB drive "old" 0.060
And process "udev-watchdog" is running 0.078
And udev-watchdog is monitoring the correct device 0.236
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:331 3.862
After features/support/hooks.rb:100 0.010
Tags: @product
1:37.925
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.176
And I start Tails from USB drive "old" with network unplugged and I login 1:2.278
Then Tails is running from USB drive "old" 0.278
And I create a persistent partition 25.873
And I take note of which tps features are available 1.189
Then a Tails persistence partition exists on USB drive "old" 0.665
And I shutdown Tails and wait for the computer to power off 7.464
After features/support/hooks.rb:331 0.532
After features/support/hooks.rb:100 0.009
Tags: @product
1:35.920
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.190
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:8.651
Then Tails is running from USB drive "old" 0.277
And all tps features are active 1.733
When I write some files expected to persist 1.409
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.206
And all persistence configuration files have safe access rights 0.363
And all persistent directories from the old Tails version have safe access rights 2.100
And I take note of which tps features are available 0.448
And I shutdown Tails and wait for the computer to power off 3.175
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.364
After features/support/hooks.rb:331 0.436
After features/support/hooks.rb:100 0.009
Tags: @product
2:30.695
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.230
And I log in to a new session 15.051
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.306
And I plug USB drive "to_upgrade" 2.488
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.197
Then the running Tails is installed on USB drive "to_upgrade" 20.043
And I unplug USB drive "to_upgrade" 0.191
And I unplug USB drive "__internal" 0.186
After features/support/hooks.rb:331 3.808
After features/support/hooks.rb:100 0.000
Tags: @product
1:24.720
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.188
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:16.718
Then all tps features from the old Tails version are active 1.298
And Tails is running from USB drive "to_upgrade" 0.272
And the boot device has safe access rights 2.900
And the expected persistent files created with the old Tails version are present in the filesystem 1.277
And all persistent directories from the old Tails version have safe access rights 2.064
After features/support/hooks.rb:331 0.691
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
4:10.194
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.933
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.249
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.248
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.051
And Tor is ready 17.217
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.614
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.051
Given I shutdown Tails and wait for the computer to power off 11.002
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:12.962
Then Tails is running version 6.2~testoverlayfs 0.032
And all tps features are active 1.913
And the file system changes introduced in version 6.2~testoverlayfs are present 0.251
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.211
When the network is plugged 0.059
And Tor is ready 11.884
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.636
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.557
Given I shutdown Tails and wait for the computer to power off 7.475
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.700
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 1.928
And the file system changes introduced in version 6.3~testoverlayfs are present 0.466
And only the 6.3~testoverlayfs SquashFS delta is installed 0.069
# 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.145
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.238
When the network is plugged 0.053
And Tor is ready 10.205
Then the Upgrader considers the system as up-to-date 10.584
# 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.160
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.550
After features/support/hooks.rb:331 0.829
After features/support/hooks.rb:100 0.018
Tags: @product @automatic_upgrade
21.820
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 9.918
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.268
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.060
But a current signing key is available on our website 0.000
When the network is plugged 0.055
And Tor is ready 10.918
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.555
After features/support/hooks.rb:331 1.068
After features/support/hooks.rb:100 0.000