Project Number Date
test_Tails_ISO_stable 5921 30 Oct 2025, 18:13

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:9.810 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:59.393
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.224
And I create a 7200 MiB disk named "old" 0.063
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 27.321
When I start Tails from USB drive "old" with network unplugged 1:26.477
Then the boot device has safe access rights 3.243
And Tails is running from USB drive "old" 0.339
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.307
And I unplug USB drive "old" 0.203
After features/support/hooks.rb:331 4.069
After features/support/hooks.rb:100 0.014
Tags: @product
2:10.615
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.229
And I start Tails from USB drive "old" with network unplugged and I login 1:29.710
Then Tails is running from USB drive "old" 0.764
And I create a persistent partition 29.675
And I take note of which tps features are available 1.318
Then a Tails persistence partition exists on USB drive "old" 0.698
And I shutdown Tails and wait for the computer to power off 8.218
After features/support/hooks.rb:331 0.389
After features/support/hooks.rb:100 0.015
Tags: @product
2:22.432
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.234
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:43.486
Then Tails is running from USB drive "old" 0.888
And all tps features are active 7.059
When I write some files expected to persist 1.648
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.217
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 2.948
And I take note of which tps features are available 0.663
And I shutdown Tails and wait for the computer to power off 5.223
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.733
After features/support/hooks.rb:331 0.634
After features/support/hooks.rb:100 0.009
Tags: @product
2:41.630
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.440
And I log in to a new session 18.431
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.391
And I plug USB drive "to_upgrade" 2.865
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:43.875
Then the running Tails is installed on USB drive "to_upgrade" 22.233
And I unplug USB drive "to_upgrade" 0.186
And I unplug USB drive "__internal" 0.207
After features/support/hooks.rb:331 3.941
After features/support/hooks.rb:100 0.000
Tags: @product
1:54.056
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:43.765
Then all tps features from the old Tails version are active 1.585
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 4.000
And the expected persistent files created with the old Tails version are present in the filesystem 1.525
And all persistent directories from the old Tails version have safe access rights 2.661
After features/support/hooks.rb:331 1.024
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
5:35.035
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.028
And no SquashFS delta is installed 0.151
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.634
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.256
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.461
When the network is plugged 0.075
And Tor is ready 43.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.919
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.999
Given I shutdown Tails and wait for the computer to power off 8.664
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.471
Then Tails is running version 6.2~testoverlayfs 0.010
And all tps features are active 2.620
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.079
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.181
# 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.244
When the network is plugged 0.089
And Tor is ready 11.863
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.923
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.386
Given I shutdown Tails and wait for the computer to power off 3.126
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.659
Then Tails is running version 6.3~testoverlayfs 0.009
And all tps features are active 2.938
And the file system changes introduced in version 6.3~testoverlayfs are present 0.648
And only the 6.3~testoverlayfs SquashFS delta is installed 0.061
# 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.182
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.062
And Tor is ready 11.941
Then the Upgrader considers the system as up-to-date 0.260
# 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.566
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.519
After features/support/hooks.rb:331 1.455
After features/support/hooks.rb:100 0.020
Tags: @product @automatic_upgrade
26.645
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.778
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.291
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the signing key used by the Upgrader is outdated 0.080
But a current signing key is available on our website 0.000
When the network is plugged 0.083
And Tor is ready 12.664
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.683
After features/support/hooks.rb:331 0.730
After features/support/hooks.rb:100 0.000