Project Number Date
test_Tails_ISO_devel 4333 10 Apr 2026, 11:24

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:37.523 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:6.441
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 14.631
When I start Tails from USB drive "old" with network unplugged 47.084
Then the boot device has safe access rights 2.897
And Tails is running from USB drive "old" 0.273
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.059
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:331 1.560
After features/support/hooks.rb:100 0.008
Tags: @product
1:29.369
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 54.987
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.503
And I take note of which tps features are available 0.633
Then a Tails persistence partition exists on USB drive "old" 0.526
And I shutdown Tails and wait for the computer to power off 8.371
After features/support/hooks.rb:331 0.499
After features/support/hooks.rb:100 0.009
Tags: @product
1:30.336
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.467
Then Tails is running from USB drive "old" 0.306
And all tps features are active 1.285
When I write some files expected to persist 1.408
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.496
And all persistent directories from the old Tails version have safe access rights 1.779
And I take note of which tps features are available 0.157
And I shutdown Tails and wait for the computer to power off 8.484
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.706
After features/support/hooks.rb:331 0.506
After features/support/hooks.rb:100 0.009
Tags: @product
2:17.973
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.206
And I log in to a new session 16.861
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.972
And I plug USB drive "to_upgrade" 2.275
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.952
Then the running Tails is installed on USB drive "to_upgrade" 17.411
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.156
After features/support/hooks.rb:331 3.457
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.815
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.175
Then all tps features from the old Tails version are active 1.187
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.991
And the expected persistent files created with the old Tails version are present in the filesystem 1.256
And all persistent directories from the old Tails version have safe access rights 1.883
After features/support/hooks.rb:331 0.880
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
5:33.890
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.511
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.237
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.457
When the network is plugged 0.016
And Tor is ready 46.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.383
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 15.973
Given I shutdown Tails and wait for the computer to power off 21.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.131
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.172
And the file system changes introduced in version 6.2~testoverlayfs are present 0.253
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.245
When the network is plugged 0.018
And Tor is ready 21.819
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.388
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.350
Given I shutdown Tails and wait for the computer to power off 13.160
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.477
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.310
And the file system changes introduced in version 6.3~testoverlayfs are present 0.407
And only the 6.3~testoverlayfs SquashFS delta is installed 0.074
# 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.179
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.215
When the network is plugged 0.019
And Tor is ready 39.712
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.786
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.442
After features/support/hooks.rb:331 0.609
After features/support/hooks.rb:100 0.036
Tags: @product @automatic_upgrade
27.695
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 7.816
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
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.022
And Tor is ready 19.123
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.358
After features/support/hooks.rb:331 1.032
After features/support/hooks.rb:100 0.000