Project Number Date
test_Tails_ISO_devel 4130 19 Dec 2025, 08:15

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:57.853 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:10.665
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.077
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" 13.202
When I start Tails from USB drive "old" with network unplugged 53.185
Then the boot device has safe access rights 2.532
And Tails is running from USB drive "old" 0.227
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.053
And udev-watchdog is monitoring the correct device 0.170
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 3.717
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.105
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 51.831
Then Tails is running from USB drive "old" 0.213
And I create a persistent partition 23.996
And I take note of which tps features are available 0.734
Then a Tails persistence partition exists on USB drive "old" 0.650
And I shutdown Tails and wait for the computer to power off 6.629
After features/support/hooks.rb:331 0.230
After features/support/hooks.rb:100 0.007
Tags: @product
1:20.027
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.330
Then Tails is running from USB drive "old" 0.233
And all tps features are active 1.089
When I write some files expected to persist 1.245
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.203
And all persistence configuration files have safe access rights 0.280
And all persistent directories from the old Tails version have safe access rights 1.625
And I take note of which tps features are available 0.138
And I shutdown Tails and wait for the computer to power off 4.106
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.719
After features/support/hooks.rb:331 0.359
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.837
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.160
And I log in to a new session 12.670
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.849
And I plug USB drive "to_upgrade" 2.246
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.587
Then the running Tails is installed on USB drive "to_upgrade" 15.058
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:331 3.932
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:0.040
Then all tps features from the old Tails version are active 0.934
And Tails is running from USB drive "to_upgrade" 0.249
And the boot device has safe access rights 2.419
And the expected persistent files created with the old Tails version are present in the filesystem 1.051
And all persistent directories from the old Tails version have safe access rights 1.840
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
3:25.803
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.854
And no SquashFS delta is installed 0.114
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.301
When the network is plugged 0.018
And Tor is ready 11.861
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.921
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.054
Given I shutdown Tails and wait for the computer to power off 6.941
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.172
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.042
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.219
When the network is plugged 0.017
And Tor is ready 10.620
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.762
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.352
Given I shutdown Tails and wait for the computer to power off 7.919
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 57.461
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.157
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.117
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.015
And Tor is ready 9.781
Then the Upgrader considers the system as up-to-date 10.531
# 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.699
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.380
After features/support/hooks.rb:331 1.047
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
19.825
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.701
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
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 8.227
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.571
After features/support/hooks.rb:331 0.908
After features/support/hooks.rb:100 0.000