Project Number Date
test_Tails_ISO_devel 4467 24 Jun 2026, 11: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:11.978 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:14.707
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.055
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.373
When I start Tails from USB drive "old" with network unplugged 57.068
Then the boot device has safe access rights 2.464
And Tails is running from USB drive "old" 0.213
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.075
And udev-watchdog is monitoring the correct device 0.229
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 3.895
After features/support/hooks.rb:108 0.015
Tags: @product
1:32.743
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login 53.841
Then Tails is running from USB drive "old" 0.252
And I create a persistent partition 25.286
And I take note of which tps features are available 4.450
Then a Tails persistence partition exists on USB drive "old" 0.630
And I shutdown Tails and wait for the computer to power off 8.179
After features/support/hooks.rb:339 0.200
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.309
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.320
Then Tails is running from USB drive "old" 0.276
And all tps features are active 5.488
When I write some files expected to persist 1.431
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.170
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.021
And I take note of which tps features are available 3.866
And I shutdown Tails and wait for the computer to power off 4.168
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.161
After features/support/hooks.rb:339 0.514
After features/support/hooks.rb:108 0.007
Tags: @product
2:10.982
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.923
And I log in to a new session 12.177
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.810
And I plug USB drive "to_upgrade" 2.212
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.831
Then the running Tails is installed on USB drive "to_upgrade" 15.629
And I unplug USB drive "to_upgrade" 0.269
And I unplug USB drive "__internal" 0.130
After features/support/hooks.rb:339 1.977
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.648
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.050
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.228
Then all tps features from the old Tails version are active 1.020
And Tails is running from USB drive "to_upgrade" 0.274
And the boot device has safe access rights 2.544
And the expected persistent files created with the old Tails version are present in the filesystem 1.147
And all persistent directories from the old Tails version have safe access rights 2.382
After features/support/hooks.rb:339 0.644
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:1.918
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.514
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.252
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
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.389
When the network is plugged 0.020
And Tor is ready 13.485
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.240
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.869
Given I shutdown Tails and wait for the computer to power off 9.436
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.263
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 5.118
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.214
When the network is plugged 0.016
And Tor is ready 10.319
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.329
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.819
Given I shutdown Tails and wait for the computer to power off 8.193
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.737
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.014
And the file system changes introduced in version 6.3~testoverlayfs are present 0.373
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.195
When the network is plugged 0.015
And Tor is ready 10.324
Then the Upgrader considers the system as up-to-date 10.580
# 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.716
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.493
After features/support/hooks.rb:339 1.051
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
20.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.608
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.065
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 10.021
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.685
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.000