Project Number Date
test_Tails_ISO_devel 4198 29 Jan 2026, 12:39

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:57.068 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:34.443
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.330
And I create a 7200 MiB disk named "old" 0.046
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 36.209
When I start Tails from USB drive "old" with network unplugged 52.734
Then the boot device has safe access rights 3.213
And Tails is running from USB drive "old" 0.307
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.228
And I unplug USB drive "old" 0.192
After features/support/hooks.rb:331 3.873
After features/support/hooks.rb:100 0.008
Tags: @product
1:40.877
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.162
And I start Tails from USB drive "old" with network unplugged and I login 1:2.020
Then Tails is running from USB drive "old" 0.330
And I create a persistent partition 28.808
And I take note of which tps features are available 1.186
Then a Tails persistence partition exists on USB drive "old" 0.693
And I shutdown Tails and wait for the computer to power off 7.676
After features/support/hooks.rb:331 0.588
After features/support/hooks.rb:100 0.008
Tags: @product
1:45.846
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:13.526
Then Tails is running from USB drive "old" 0.318
And all tps features are active 1.911
When I write some files expected to persist 1.402
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.219
And all persistence configuration files have safe access rights 0.319
And all persistent directories from the old Tails version have safe access rights 2.285
And I take note of which tps features are available 0.433
And I shutdown Tails and wait for the computer to power off 7.490
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 17.772
After features/support/hooks.rb:331 0.553
After features/support/hooks.rb:100 0.009
Tags: @product
2:40.430
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 10.930
And I log in to a new session 13.089
And I clone USB drive "old" to a new USB drive "to_upgrade" 10.332
And I plug USB drive "to_upgrade" 2.665
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:42.283
Then the running Tails is installed on USB drive "to_upgrade" 20.684
And I unplug USB drive "to_upgrade" 0.181
And I unplug USB drive "__internal" 0.261
After features/support/hooks.rb:331 2.330
After features/support/hooks.rb:100 0.000
Tags: @product
1:23.851
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.170
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.134
Then all tps features from the old Tails version are active 1.381
And Tails is running from USB drive "to_upgrade" 0.361
And the boot device has safe access rights 3.128
And the expected persistent files created with the old Tails version are present in the filesystem 1.361
And all persistent directories from the old Tails version have safe access rights 2.313
After features/support/hooks.rb:331 0.697
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
4:27.998
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 12.204
And no SquashFS delta is installed 0.135
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.312
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.450
When the network is plugged 0.078
And Tor is ready 13.595
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.737
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 10.256
Given I shutdown Tails and wait for the computer to power off 12.570
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:24.089
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 2.196
And the file system changes introduced in version 6.2~testoverlayfs are present 0.311
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.207
# 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.272
When the network is plugged 0.059
And Tor is ready 12.801
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.820
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 7.061
Given I shutdown Tails and wait for the computer to power off 7.668
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:18.913
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 2.094
And the file system changes introduced in version 6.3~testoverlayfs are present 0.487
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.161
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.216
When the network is plugged 0.082
And Tor is ready 12.237
Then the Upgrader considers the system as up-to-date 0.124
# 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.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.562
After features/support/hooks.rb:331 1.117
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
23.620
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 10.767
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.270
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.074
And the signing key used by the Upgrader is outdated 0.079
But a current signing key is available on our website 0.000
When the network is plugged 0.057
And Tor is ready 10.328
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.041
After features/support/hooks.rb:331 0.815
After features/support/hooks.rb:100 0.000