Project Number Date
test_Tails_ISO_devel 4304 30 Mar 2026, 11:05

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:5.432 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:4.622
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.205
When I start Tails from USB drive "old" with network unplugged 47.041
Then the boot device has safe access rights 2.589
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.104
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:331 1.132
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.338
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login 52.113
Then Tails is running from USB drive "old" 0.233
And I create a persistent partition 23.582
And I take note of which tps features are available 0.661
Then a Tails persistence partition exists on USB drive "old" 0.534
And I shutdown Tails and wait for the computer to power off 8.161
After features/support/hooks.rb:331 0.529
After features/support/hooks.rb:100 0.007
Tags: @product
1:23.624
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 "old" with network unplugged and I login with persistence enabled 58.762
Then Tails is running from USB drive "old" 0.239
And all tps features are active 1.155
When I write some files expected to persist 1.265
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.169
And all persistence configuration files have safe access rights 0.432
And all persistent directories from the old Tails version have safe access rights 1.740
And I take note of which tps features are available 0.223
And I shutdown Tails and wait for the computer to power off 7.838
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.749
After features/support/hooks.rb:331 0.187
After features/support/hooks.rb:100 0.006
Tags: @product
2:10.047
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 without a persistent partition and stopped at Tails Greeter's login screen 8.036
And I log in to a new session 12.970
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.774
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.376
Then the running Tails is installed on USB drive "to_upgrade" 14.416
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.138
After features/support/hooks.rb:331 2.293
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.213
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.322
Then all tps features from the old Tails version are active 0.990
And Tails is running from USB drive "to_upgrade" 0.274
And the boot device has safe access rights 2.468
And the expected persistent files created with the old Tails version are present in the filesystem 1.175
And all persistent directories from the old Tails version have safe access rights 1.923
After features/support/hooks.rb:331 0.642
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:30.273
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.035
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.239
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.358
When the network is plugged 0.014
And Tor is ready 21.251
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.346
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.803
Given I shutdown Tails and wait for the computer to power off 19.678
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.687
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.056
And the file system changes introduced in version 6.2~testoverlayfs are present 0.211
And only the 6.2~testoverlayfs SquashFS delta is installed 0.039
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.213
When the network is plugged 0.018
And Tor is ready 20.004
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.408
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.891
Given I shutdown Tails and wait for the computer to power off 16.977
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.505
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.060
And the file system changes introduced in version 6.3~testoverlayfs are present 0.337
And only the 6.3~testoverlayfs SquashFS delta is installed 0.045
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.206
When the network is plugged 0.014
And Tor is ready 21.327
Then the Upgrader considers the system as up-to-date 0.121
# 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.428
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.388
After features/support/hooks.rb:331 0.703
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
25.313
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.671
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.013
And Tor is ready 16.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.394
After features/support/hooks.rb:331 1.132
After features/support/hooks.rb:100 0.000