Project Number Date
test_Tails_ISO_devel 4150 05 Jan 2026, 11:23

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 10:26.254 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
57.759
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.051
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.900
When I start Tails from USB drive "old" with network unplugged 40.670
Then the boot device has safe access rights 2.446
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.219
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:331 3.875
After features/support/hooks.rb:100 0.006
Tags: @product
1:18.952
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.056
And I start Tails from USB drive "old" with network unplugged and I login 50.091
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 23.239
And I take note of which tps features are available 0.633
Then a Tails persistence partition exists on USB drive "old" 0.475
And I shutdown Tails and wait for the computer to power off 4.207
After features/support/hooks.rb:331 0.445
After features/support/hooks.rb:100 0.025
Tags: @product
1:20.803
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 56.077
Then Tails is running from USB drive "old" 0.224
And all tps features are active 1.175
When I write some files expected to persist 1.234
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.862
And I take note of which tps features are available 0.139
And I shutdown Tails and wait for the computer to power off 7.814
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.757
After features/support/hooks.rb:331 0.484
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.420
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 7.717
And I log in to a new session 11.705
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.822
And I plug USB drive "to_upgrade" 2.235
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.395
Then the running Tails is installed on USB drive "to_upgrade" 14.258
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.145
After features/support/hooks.rb:331 3.867
After features/support/hooks.rb:100 0.000
Tags: @product
1:5.955
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.048
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.162
Then all tps features from the old Tails version are active 0.967
And Tails is running from USB drive "to_upgrade" 0.281
And the boot device has safe access rights 2.425
And the expected persistent files created with the old Tails version are present in the filesystem 1.069
And all persistent directories from the old Tails version have safe access rights 1.999
After features/support/hooks.rb:331 0.801
After features/support/hooks.rb:100 0.008
3:16.827
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 8.111
And no SquashFS delta is installed 0.077
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.226
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.228
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.316
When the network is plugged 0.041
And Tor is ready 13.323
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.302
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.059
Given I shutdown Tails and wait for the computer to power off 9.420
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.712
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.066
And the file system changes introduced in version 6.2~testoverlayfs are present 0.195
And only the 6.2~testoverlayfs SquashFS delta is installed 0.045
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.204
# 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.018
And Tor is ready 10.500
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.735
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.198
Given I shutdown Tails and wait for the computer to power off 4.176
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.050
Then Tails is running version 6.3~testoverlayfs 0.017
And all tps features are active 1.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.409
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.016
And Tor is ready 10.924
Then the Upgrader considers the system as up-to-date 0.103
# 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.209
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.398
After features/support/hooks.rb:331 1.034
After features/support/hooks.rb:100 0.011
17.535
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 with a persistent partition enabled and logged in 7.581
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.304
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.350
After features/support/hooks.rb:331 0.739
After features/support/hooks.rb:100 0.000