Project Number Date
test_Tails_ISO_devel 4379 06 May 2026, 10:51

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:12.949 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:8.675
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.345
When I start Tails from USB drive "old" with network unplugged 50.876
Then the boot device has safe access rights 2.727
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.058
And udev-watchdog is monitoring the correct device 0.196
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:331 1.311
After features/support/hooks.rb:100 0.006
Tags: @product
1:26.742
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.047
And I start Tails from USB drive "old" with network unplugged and I login 52.336
Then Tails is running from USB drive "old" 0.239
And I create a persistent partition 24.793
And I take note of which tps features are available 0.674
Then a Tails persistence partition exists on USB drive "old" 0.483
And I shutdown Tails and wait for the computer to power off 8.168
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.006
Tags: @product
1:23.590
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.808
Then Tails is running from USB drive "old" 0.245
And all tps features are active 1.063
When I write some files expected to persist 1.091
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.154
And all persistence configuration files have safe access rights 0.383
And all persistent directories from the old Tails version have safe access rights 1.774
And I take note of which tps features are available 0.166
And I shutdown Tails and wait for the computer to power off 8.096
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.748
After features/support/hooks.rb:331 0.236
After features/support/hooks.rb:100 0.006
Tags: @product
2:9.123
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 7.407
And I log in to a new session 11.738
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.699
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.746
Then the running Tails is installed on USB drive "to_upgrade" 15.015
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.150
After features/support/hooks.rb:331 2.117
After features/support/hooks.rb:100 0.000
Tags: @product
1:7.594
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.292
Then all tps features from the old Tails version are active 0.913
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.381
And the expected persistent files created with the old Tails version are present in the filesystem 1.089
And all persistent directories from the old Tails version have safe access rights 1.661
After features/support/hooks.rb:331 0.622
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:33.154
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 8.289
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
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.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.026
And Tor is ready 22.156
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.393
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.461
Given I shutdown Tails and wait for the computer to power off 19.809
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.554
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.170
And the file system changes introduced in version 6.2~testoverlayfs are present 0.220
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.135
# 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.201
When the network is plugged 0.012
And Tor is ready 21.687
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 4.706
Given I shutdown Tails and wait for the computer to power off 18.371
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.045
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.121
And the file system changes introduced in version 6.3~testoverlayfs are present 0.353
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.017
And Tor is ready 19.902
Then the Upgrader considers the system as up-to-date 0.099
# 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.325
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.353
After features/support/hooks.rb:331 0.800
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
24.068
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.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.290
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
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.014
And Tor is ready 16.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 0.682
After features/support/hooks.rb:100 0.000