Project Number Date
test_Tails_ISO_stable 6714 01 Oct 2026, 11:17

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:58.285 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:13.735
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.105
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.316
When I start Tails from USB drive "old" with network unplugged 56.706
Then the boot device has safe access rights 2.034
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.123
And I unplug USB drive "old" 0.110
After features/support/hooks.rb:339 4.027
After features/support/hooks.rb:108 0.005
Tags: @product
1:17.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 45.732
Then Tails is running from USB drive "old" 0.217
And I create a persistent partition 22.033
And I take note of which tps features are available 5.865
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 2.591
After features/support/hooks.rb:339 0.265
After features/support/hooks.rb:108 0.015
Tags: @product
1:28.044
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.095
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.164
Then Tails is running from USB drive "old" 0.228
And all tps features are active 7.190
When I write some files expected to persist 0.886
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.186
And all persistence configuration files have safe access rights 0.228
And all persistent directories from the old Tails version have safe access rights 1.316
And I take note of which tps features are available 5.775
And I shutdown Tails and wait for the computer to power off 2.539
# 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" 11.432
After features/support/hooks.rb:339 0.294
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.409
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 8.109
And I log in to a new session 10.173
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.616
And I plug USB drive "to_upgrade" 2.172
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.345
Then the running Tails is installed on USB drive "to_upgrade" 17.774
And I unplug USB drive "to_upgrade" 0.111
And I unplug USB drive "__internal" 0.104
After features/support/hooks.rb:339 1.651
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.154
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.255
Then all tps features from the old Tails version are active 1.059
And Tails is running from USB drive "to_upgrade" 0.182
And the boot device has safe access rights 2.224
And the expected persistent files created with the old Tails version are present in the filesystem 0.779
And all persistent directories from the old Tails version have safe access rights 1.572
After features/support/hooks.rb:339 0.461
After features/support/hooks.rb:108 0.005
3:25.736
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.861
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.159
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.160
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.305
When the network is plugged 0.023
And Tor is ready 12.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.979
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.878
Given I shutdown Tails and wait for the computer to power off 5.403
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.924
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 7.647
And the file system changes introduced in version 6.2~testoverlayfs are present 0.196
And only the 6.2~testoverlayfs SquashFS delta is installed 0.054
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.098
# 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.165
When the network is plugged 0.033
And Tor is ready 11.160
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.327
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.594
Given I shutdown Tails and wait for the computer to power off 5.128
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.472
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.397
And the file system changes introduced in version 6.3~testoverlayfs are present 0.296
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.203
When the network is plugged 0.034
And Tor is ready 10.049
Then the Upgrader considers the system as up-to-date 0.111
# 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 3.082
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.300
After features/support/hooks.rb:339 0.535
After features/support/hooks.rb:108 0.026
19.161
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.905
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the signing key used by the Upgrader is outdated 0.043
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 9.523
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.373
After features/support/hooks.rb:339 0.519
After features/support/hooks.rb:108 0.000