Project Number Date
test_Tails_ISO_stable 5945 12 Nov 2025, 08:22

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:31.597 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
2:10.842
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 1.377
And I create a 7200 MiB disk named "old" 0.136
And I plug USB drive "old" 1.066
And I write an old version of the Tails USB image to disk "old" 35.325
When I start Tails from USB drive "old" with network unplugged 1:29.116
Then the boot device has safe access rights 2.957
And Tails is running from USB drive "old" 0.313
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.180
After features/support/hooks.rb:331 4.990
After features/support/hooks.rb:100 0.008
Tags: @product
2:19.773
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.222
And I start Tails from USB drive "old" with network unplugged and I login 1:33.594
Then Tails is running from USB drive "old" 0.653
And I create a persistent partition 35.050
And I take note of which tps features are available 1.161
Then a Tails persistence partition exists on USB drive "old" 0.689
And I shutdown Tails and wait for the computer to power off 8.401
After features/support/hooks.rb:331 0.327
After features/support/hooks.rb:100 0.008
Tags: @product
2:29.598
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.184
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:49.966
Then Tails is running from USB drive "old" 0.289
And all tps features are active 2.101
When I write some files expected to persist 1.697
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.404
And all persistent directories from the old Tails version have safe access rights 3.999
And I take note of which tps features are available 0.638
And I shutdown Tails and wait for the computer to power off 10.924
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 19.190
After features/support/hooks.rb:331 0.408
After features/support/hooks.rb:100 0.011
Tags: @product
2:44.477
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 16.489
And I log in to a new session 18.868
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.550
And I plug USB drive "to_upgrade" 2.319
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.170
Then the running Tails is installed on USB drive "to_upgrade" 22.639
And I unplug USB drive "to_upgrade" 0.207
And I unplug USB drive "__internal" 0.230
After features/support/hooks.rb:331 4.908
After features/support/hooks.rb:100 0.000
Tags: @product
1:50.229
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.176
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:40.341
Then all tps features from the old Tails version are active 2.276
And Tails is running from USB drive "to_upgrade" 0.373
And the boot device has safe access rights 3.480
And the expected persistent files created with the old Tails version are present in the filesystem 1.419
And all persistent directories from the old Tails version have safe access rights 2.160
After features/support/hooks.rb:331 0.858
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:29.891
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 14.864
And no SquashFS delta is installed 0.121
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.295
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.255
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.054
And Tor is ready 14.126
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.794
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 8.790
Given I shutdown Tails and wait for the computer to power off 12.803
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:47.604
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 2.403
And the file system changes introduced in version 6.2~testoverlayfs are present 0.287
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.303
When the network is plugged 0.230
And Tor is ready 12.667
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.851
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.967
Given I shutdown Tails and wait for the computer to power off 8.153
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:43.022
Then Tails is running version 6.3~testoverlayfs 0.014
And all tps features are active 2.388
And the file system changes introduced in version 6.3~testoverlayfs are present 0.417
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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.066
And Tor is ready 12.144
Then the Upgrader considers the system as up-to-date 10.893
# 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.667
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.557
After features/support/hooks.rb:331 0.889
After features/support/hooks.rb:100 0.045
Tags: @product @automatic_upgrade
26.784
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.038
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.305
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.093
And the signing key used by the Upgrader is outdated 0.073
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 12.511
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.702
After features/support/hooks.rb:331 1.115
After features/support/hooks.rb:100 0.000