Project Number Date
test_Tails_ISO_devel 4094 30 Nov 2025, 17:42

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 16:44.047 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:51.458
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.168
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.040
And I write an old version of the Tails USB image to disk "old" 31.987
When I start Tails from USB drive "old" with network unplugged 1:13.939
Then the boot device has safe access rights 3.329
And Tails is running from USB drive "old" 0.370
And there is no persistence partition on USB drive "old" 0.066
And process "udev-watchdog" is running 0.066
And udev-watchdog is monitoring the correct device 0.273
And I unplug USB drive "old" 0.168
After features/support/hooks.rb:331 3.945
After features/support/hooks.rb:100 0.008
Tags: @product
2:8.735
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.163
And I start Tails from USB drive "old" with network unplugged and I login 1:27.314
Then Tails is running from USB drive "old" 0.412
And I create a persistent partition 31.087
And I take note of which tps features are available 1.218
Then a Tails persistence partition exists on USB drive "old" 0.672
And I shutdown Tails and wait for the computer to power off 7.866
After features/support/hooks.rb:331 0.358
After features/support/hooks.rb:100 0.010
Tags: @product
2:19.045
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.221
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:36.586
Then Tails is running from USB drive "old" 0.276
And all tps features are active 2.255
When I write some files expected to persist 1.728
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.296
And all persistence configuration files have safe access rights 0.380
And all persistent directories from the old Tails version have safe access rights 2.437
And I take note of which tps features are available 6.929
And I shutdown Tails and wait for the computer to power off 8.274
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.657
After features/support/hooks.rb:331 0.444
After features/support/hooks.rb:100 0.008
Tags: @product
2:55.607
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 27.068
And I log in to a new session 17.139
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.934
And I plug USB drive "to_upgrade" 2.449
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.803
Then the running Tails is installed on USB drive "to_upgrade" 20.816
And I unplug USB drive "to_upgrade" 0.189
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 3.939
After features/support/hooks.rb:100 0.000
Tags: @product
1:52.766
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.171
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:42.384
Then all tps features from the old Tails version are active 3.043
And Tails is running from USB drive "to_upgrade" 0.366
And the boot device has safe access rights 3.256
And the expected persistent files created with the old Tails version are present in the filesystem 1.276
And all persistent directories from the old Tails version have safe access rights 2.267
After features/support/hooks.rb:331 0.724
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:10.361
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 13.368
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.298
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.453
When the network is plugged 0.067
And Tor is ready 14.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.990
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 7.491
Given I shutdown Tails and wait for the computer to power off 11.428
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.159
Then Tails is running version 6.2~testoverlayfs 0.014
And all tps features are active 2.458
And the file system changes introduced in version 6.2~testoverlayfs are present 0.291
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# 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.217
When the network is plugged 0.077
And Tor is ready 11.008
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.823
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.409
Given I shutdown Tails and wait for the computer to power off 7.721
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:44.121
Then Tails is running version 6.3~testoverlayfs 0.010
And all tps features are active 2.285
And the file system changes introduced in version 6.3~testoverlayfs are present 0.510
And only the 6.3~testoverlayfs SquashFS delta is installed 0.072
# 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.162
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.254
When the network is plugged 0.058
And Tor is ready 13.060
Then the Upgrader considers the system as up-to-date 0.214
# 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.658
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.637
After features/support/hooks.rb:331 0.842
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
26.072
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 11.935
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 signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.054
And Tor is ready 11.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.727
After features/support/hooks.rb:331 0.811
After features/support/hooks.rb:100 0.000