Project Number Date
test_Tails_ISO_devel 4316 03 Apr 2026, 11:32

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:28.644 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.154
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 15.027
When I start Tails from USB drive "old" with network unplugged 54.254
Then the boot device has safe access rights 3.094
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.192
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:331 3.504
After features/support/hooks.rb:100 0.015
Tags: @product
1:34.462
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 58.293
Then Tails is running from USB drive "old" 0.286
And I create a persistent partition 25.623
And I take note of which tps features are available 0.749
Then a Tails persistence partition exists on USB drive "old" 0.714
And I shutdown Tails and wait for the computer to power off 8.717
After features/support/hooks.rb:331 0.494
After features/support/hooks.rb:100 0.008
Tags: @product
1:28.037
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.786
Then Tails is running from USB drive "old" 0.284
And all tps features are active 1.113
When I write some files expected to persist 1.427
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.228
And all persistence configuration files have safe access rights 0.468
And all persistent directories from the old Tails version have safe access rights 2.144
And I take note of which tps features are available 0.321
And I shutdown Tails and wait for the computer to power off 4.219
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.974
After features/support/hooks.rb:331 0.324
After features/support/hooks.rb:100 0.006
Tags: @product
2:22.168
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 9.111
And I log in to a new session 18.803
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.034
And I plug USB drive "to_upgrade" 2.263
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.121
Then the running Tails is installed on USB drive "to_upgrade" 17.483
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 4.054
After features/support/hooks.rb:100 0.000
Tags: @product
1:19.860
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:11.638
Then all tps features from the old Tails version are active 1.161
And Tails is running from USB drive "to_upgrade" 0.320
And the boot device has safe access rights 2.769
And the expected persistent files created with the old Tails version are present in the filesystem 1.482
And all persistent directories from the old Tails version have safe access rights 2.428
After features/support/hooks.rb:331 0.955
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
5:1.625
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 9.367
And no SquashFS delta is installed 0.132
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.324
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.277
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.364
When the network is plugged 0.016
And Tor is ready 30.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.437
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.205
Given I shutdown Tails and wait for the computer to power off 19.027
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:20.652
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.227
And the file system changes introduced in version 6.2~testoverlayfs are present 0.245
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.128
# 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.227
When the network is plugged 0.014
And Tor is ready 21.709
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.387
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.939
Given I shutdown Tails and wait for the computer to power off 17.911
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:17.463
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.187
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.175
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.331
When the network is plugged 0.018
And Tor is ready 21.126
Then the Upgrader considers the system as up-to-date 0.142
# 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 5.016
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.469
After features/support/hooks.rb:331 1.076
After features/support/hooks.rb:100 0.015
Tags: @product @automatic_upgrade
28.335
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.766
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.331
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 19.704
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.414
After features/support/hooks.rb:331 1.105
After features/support/hooks.rb:100 0.000