Project Number Date
test_Tails_ISO_devel 4295 26 Mar 2026, 13:43

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:16.525 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:4.737
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 14.896
When I start Tails from USB drive "old" with network unplugged 44.899
Then the boot device has safe access rights 3.052
And Tails is running from USB drive "old" 0.316
And there is no persistence partition on USB drive "old" 0.061
And process "udev-watchdog" is running 0.069
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.141
After features/support/hooks.rb:331 1.184
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.078
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 56.403
Then Tails is running from USB drive "old" 0.265
And I create a persistent partition 25.268
And I take note of which tps features are available 0.809
Then a Tails persistence partition exists on USB drive "old" 0.775
And I shutdown Tails and wait for the computer to power off 8.495
After features/support/hooks.rb:331 0.335
After features/support/hooks.rb:100 0.009
Tags: @product
1:32.388
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.543
Then Tails is running from USB drive "old" 0.261
And all tps features are active 1.216
When I write some files expected to persist 1.423
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.157
And all persistence configuration files have safe access rights 0.577
And all persistent directories from the old Tails version have safe access rights 2.198
And I take note of which tps features are available 0.236
And I shutdown Tails and wait for the computer to power off 8.707
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.987
After features/support/hooks.rb:331 0.477
After features/support/hooks.rb:100 0.007
Tags: @product
2:20.886
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.687
And I log in to a new session 17.715
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.819
And I plug USB drive "to_upgrade" 2.249
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.900
Then the running Tails is installed on USB drive "to_upgrade" 17.158
And I unplug USB drive "to_upgrade" 0.175
And I unplug USB drive "__internal" 0.180
After features/support/hooks.rb:331 3.860
After features/support/hooks.rb:100 0.000
Tags: @product
1:18.212
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.078
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.262
Then all tps features from the old Tails version are active 1.207
And Tails is running from USB drive "to_upgrade" 0.273
And the boot device has safe access rights 3.036
And the expected persistent files created with the old Tails version are present in the filesystem 1.374
And all persistent directories from the old Tails version have safe access rights 1.980
After features/support/hooks.rb:331 0.662
After features/support/hooks.rb:100 0.025
Tags: @product @automatic_upgrade
4:45.000
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 9.423
And no SquashFS delta is installed 0.195
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.544
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.391
When the network is plugged 0.015
And Tor is ready 23.892
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.452
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.661
Given I shutdown Tails and wait for the computer to power off 20.364
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.724
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.185
And the file system changes introduced in version 6.2~testoverlayfs are present 0.365
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.172
# 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.311
When the network is plugged 0.035
And Tor is ready 21.747
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.440
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.013
Given I shutdown Tails and wait for the computer to power off 18.173
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:19.231
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.483
And the file system changes introduced in version 6.3~testoverlayfs are present 0.431
And only the 6.3~testoverlayfs SquashFS delta is installed 0.082
# 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.174
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.223
When the network is plugged 0.018
And Tor is ready 20.422
Then the Upgrader considers the system as up-to-date 0.128
# 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 4.810
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.443
After features/support/hooks.rb:331 1.138
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
43.221
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.539
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.082
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 20.794
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.406
After features/support/hooks.rb:331 0.830
After features/support/hooks.rb:100 0.000