Project Number Date
test_Tails_ISO_devel 4270 10 Mar 2026, 08:01

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:38.326 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:43.173
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.068
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.660
When I start Tails from USB drive "old" with network unplugged 1:24.933
Then the boot device has safe access rights 2.819
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.204
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 3.583
After features/support/hooks.rb:100 0.052
Tags: @product
1:27.177
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 54.806
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 23.053
And I take note of which tps features are available 0.651
Then a Tails persistence partition exists on USB drive "old" 0.528
And I shutdown Tails and wait for the computer to power off 7.853
After features/support/hooks.rb:331 0.149
After features/support/hooks.rb:100 0.006
Tags: @product
1:25.858
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.046
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.525
Then Tails is running from USB drive "old" 0.240
And all tps features are active 1.058
When I write some files expected to persist 1.350
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 1.875
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 7.860
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.081
After features/support/hooks.rb:331 0.527
After features/support/hooks.rb:100 0.006
Tags: @product
2:28.300
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 9.016
And I log in to a new session 16.093
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.871
And I plug USB drive "to_upgrade" 6.063
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:39.906
Then the running Tails is installed on USB drive "to_upgrade" 16.073
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:331 12.612
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.289
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.072
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.717
Then all tps features from the old Tails version are active 0.883
And Tails is running from USB drive "to_upgrade" 0.196
And the boot device has safe access rights 2.534
And the expected persistent files created with the old Tails version are present in the filesystem 1.102
And all persistent directories from the old Tails version have safe access rights 1.783
After features/support/hooks.rb:331 0.982
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
4:58.401
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.154
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.210
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.346
When the network is plugged 0.014
And Tor is ready 23.835
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.446
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.225
Given I shutdown Tails and wait for the computer to power off 20.227
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.790
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.097
And the file system changes introduced in version 6.2~testoverlayfs are present 0.198
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.144
# 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.215
When the network is plugged 0.025
And Tor is ready 40.881
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.356
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.731
Given I shutdown Tails and wait for the computer to power off 17.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.583
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.115
And the file system changes introduced in version 6.3~testoverlayfs are present 0.379
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.146
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.024
And Tor is ready 21.164
Then the Upgrader considers the system as up-to-date 0.096
# 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.632
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.368
After features/support/hooks.rb:331 0.727
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
26.125
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.370
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.309
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.037
And the signing key used by the Upgrader is outdated 0.053
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 17.970
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.363
After features/support/hooks.rb:331 0.612
After features/support/hooks.rb:100 0.000