Project Number Date
test_Tails_ISO_devel 4251 24 Feb 2026, 21:16

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:23.243 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:8.506
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.420
When I start Tails from USB drive "old" with network unplugged 50.690
Then the boot device has safe access rights 2.591
And Tails is running from USB drive "old" 0.283
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.077
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:331 1.317
After features/support/hooks.rb:100 0.006
Tags: @product
1:20.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 51.278
Then Tails is running from USB drive "old" 0.300
And I create a persistent partition 23.771
And I take note of which tps features are available 0.727
Then a Tails persistence partition exists on USB drive "old" 0.625
And I shutdown Tails and wait for the computer to power off 4.203
After features/support/hooks.rb:331 0.365
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.891
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.252
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.053
When I write some files expected to persist 1.159
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.198
And all persistence configuration files have safe access rights 0.285
And all persistent directories from the old Tails version have safe access rights 1.844
And I take note of which tps features are available 0.180
And I shutdown Tails and wait for the computer to power off 7.976
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.653
After features/support/hooks.rb:331 0.467
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.534
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.761
And I log in to a new session 10.205
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.708
And I plug USB drive "to_upgrade" 2.242
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.060
Then the running Tails is installed on USB drive "to_upgrade" 15.283
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:331 2.198
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.948
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.073
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.475
Then all tps features from the old Tails version are active 0.904
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.376
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.774
After features/support/hooks.rb:331 0.807
After features/support/hooks.rb:100 0.007
4:48.182
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.186
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.262
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.332
When the network is plugged 0.016
And Tor is ready 19.599
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.416
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.597
Given I shutdown Tails and wait for the computer to power off 19.986
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.567
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.228
And the file system changes introduced in version 6.2~testoverlayfs are present 0.214
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.175
When the network is plugged 0.019
And Tor is ready 41.141
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.376
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.447
Given I shutdown Tails and wait for the computer to power off 17.394
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.700
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.109
And the file system changes introduced in version 6.3~testoverlayfs are present 0.328
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.131
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.016
And Tor is ready 20.425
Then the Upgrader considers the system as up-to-date 0.102
# 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.277
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.365
After features/support/hooks.rb:331 0.828
After features/support/hooks.rb:100 0.046
24.224
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 7.466
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.061
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 16.004
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.396
After features/support/hooks.rb:331 1.189
After features/support/hooks.rb:100 0.000