Project Number Date
test_Tails_ISO_stable 6008 15 Dec 2025, 12:28

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:49.353 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:30.910
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.181
And I create a 7200 MiB disk named "old" 0.048
And I plug USB drive "old" 1.046
And I write an old version of the Tails USB image to disk "old" 31.657
When I start Tails from USB drive "old" with network unplugged 52.743
Then the boot device has safe access rights 4.338
And Tails is running from USB drive "old" 0.328
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.258
And I unplug USB drive "old" 0.190
After features/support/hooks.rb:331 4.144
After features/support/hooks.rb:100 0.016
Tags: @product
1:48.279
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.225
And I start Tails from USB drive "old" with network unplugged and I login 1:7.187
Then Tails is running from USB drive "old" 0.386
And I create a persistent partition 30.173
And I take note of which tps features are available 1.353
Then a Tails persistence partition exists on USB drive "old" 0.776
And I shutdown Tails and wait for the computer to power off 8.176
After features/support/hooks.rb:331 0.307
After features/support/hooks.rb:100 0.013
Tags: @product
1:53.566
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.245
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:17.312
Then Tails is running from USB drive "old" 0.296
And all tps features are active 2.101
When I write some files expected to persist 1.820
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.223
And all persistence configuration files have safe access rights 0.362
And all persistent directories from the old Tails version have safe access rights 3.416
And I take note of which tps features are available 0.503
And I shutdown Tails and wait for the computer to power off 7.868
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.415
After features/support/hooks.rb:331 0.405
After features/support/hooks.rb:100 0.009
Tags: @product
2:39.211
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 without a persistent partition and stopped at Tails Greeter's login screen 12.734
And I log in to a new session 11.078
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.763
And I plug USB drive "to_upgrade" 5.072
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.547
Then the running Tails is installed on USB drive "to_upgrade" 22.465
And I unplug USB drive "to_upgrade" 0.231
And I unplug USB drive "__internal" 0.317
After features/support/hooks.rb:331 3.663
After features/support/hooks.rb:100 0.000
Tags: @product
1:28.099
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.181
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:18.208
Then all tps features from the old Tails version are active 1.422
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 3.311
And the expected persistent files created with the old Tails version are present in the filesystem 1.366
And all persistent directories from the old Tails version have safe access rights 3.323
After features/support/hooks.rb:331 0.956
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:8.334
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 10.766
And no SquashFS delta is installed 0.066
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.218
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.420
When the network is plugged 0.074
And Tor is ready 13.037
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.664
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.751
Given I shutdown Tails and wait for the computer to power off 7.704
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.525
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.529
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.062
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.179
# 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.254
When the network is plugged 0.052
And Tor is ready 12.270
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.767
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.882
Given I shutdown Tails and wait for the computer to power off 8.178
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.086
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.628
And the file system changes introduced in version 6.3~testoverlayfs are present 0.445
And only the 6.3~testoverlayfs SquashFS delta is installed 0.070
# 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.226
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.269
When the network is plugged 0.063
And Tor is ready 12.223
Then the Upgrader considers the system as up-to-date 0.182
# 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.581
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.512
After features/support/hooks.rb:331 2.543
After features/support/hooks.rb:100 0.021
Tags: @product @automatic_upgrade
20.951
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.694
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.058
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 10.259
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.604
After features/support/hooks.rb:331 1.835
After features/support/hooks.rb:100 0.000