Project Number Date
test_Tails_ISO_devel 4156 07 Jan 2026, 11:31

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 12:37.388 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:20.106
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.070
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.437
When I start Tails from USB drive "old" with network unplugged 1:1.221
Then the boot device has safe access rights 2.594
And Tails is running from USB drive "old" 0.252
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.250
And I unplug USB drive "old" 0.148
After features/support/hooks.rb:331 3.496
After features/support/hooks.rb:100 0.007
Tags: @product
1:32.591
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.066
And I start Tails from USB drive "old" with network unplugged and I login 58.690
Then Tails is running from USB drive "old" 0.306
And I create a persistent partition 25.239
And I take note of which tps features are available 0.722
Then a Tails persistence partition exists on USB drive "old" 0.639
And I shutdown Tails and wait for the computer to power off 6.926
After features/support/hooks.rb:331 0.268
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.727
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.643
Then Tails is running from USB drive "old" 0.352
And all tps features are active 1.150
When I write some files expected to persist 1.779
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.313
And all persistence configuration files have safe access rights 0.581
And all persistent directories from the old Tails version have safe access rights 2.236
And I take note of which tps features are available 0.179
And I shutdown Tails and wait for the computer to power off 7.166
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 13.271
After features/support/hooks.rb:331 0.175
After features/support/hooks.rb:100 0.009
Tags: @product
2:15.041
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 8.368
And I log in to a new session 13.798
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.012
And I plug USB drive "to_upgrade" 2.313
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.714
Then the running Tails is installed on USB drive "to_upgrade" 16.348
And I unplug USB drive "to_upgrade" 0.271
And I unplug USB drive "__internal" 0.213
After features/support/hooks.rb:331 7.288
After features/support/hooks.rb:100 0.000
Tags: @product
1:16.638
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:7.569
Then all tps features from the old Tails version are active 1.239
And Tails is running from USB drive "to_upgrade" 0.423
And the boot device has safe access rights 3.226
And the expected persistent files created with the old Tails version are present in the filesystem 1.605
And all persistent directories from the old Tails version have safe access rights 2.495
After features/support/hooks.rb:331 0.678
After features/support/hooks.rb:100 0.066
Tags: @product @automatic_upgrade
4:19.542
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 with a persistent partition enabled and logged in 8.704
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.209
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.376
When the network is plugged 0.018
And Tor is ready 44.379
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.364
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.496
Given I shutdown Tails and wait for the computer to power off 10.011
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.525
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.500
And the file system changes introduced in version 6.2~testoverlayfs are present 0.254
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.150
# 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.199
When the network is plugged 0.017
And Tor is ready 11.270
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.762
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.752
Given I shutdown Tails and wait for the computer to power off 8.522
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.212
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.497
And the file system changes introduced in version 6.3~testoverlayfs are present 0.543
And only the 6.3~testoverlayfs SquashFS delta is installed 0.079
# 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.149
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.212
When the network is plugged 0.015
And Tor is ready 10.685
Then the Upgrader considers the system as up-to-date 10.578
# 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.229
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.410
After features/support/hooks.rb:331 1.081
After features/support/hooks.rb:100 0.024
Tags: @product @automatic_upgrade
20.741
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.188
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.251
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 9.091
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.090
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000