Project Number Date
test_Tails_ISO_stable 6267 06 Apr 2026, 14:02

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 11:54.355 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:5.395
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.057
When I start Tails from USB drive "old" with network unplugged 47.728
Then the boot device has safe access rights 2.810
And Tails is running from USB drive "old" 0.278
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.140
After features/support/hooks.rb:331 1.271
After features/support/hooks.rb:100 0.007
Tags: @product
1:24.787
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 51.889
Then Tails is running from USB drive "old" 0.221
And I create a persistent partition 23.549
And I take note of which tps features are available 0.737
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 7.838
After features/support/hooks.rb:331 0.549
After features/support/hooks.rb:100 0.008
Tags: @product
1:22.480
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.031
Then Tails is running from USB drive "old" 0.255
And all tps features are active 1.015
When I write some files expected to persist 1.199
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.409
And all persistent directories from the old Tails version have safe access rights 1.750
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 7.827
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 11.613
After features/support/hooks.rb:331 0.349
After features/support/hooks.rb:100 0.007
Tags: @product
2:10.367
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.256
And I log in to a new session 11.860
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.852
And I plug USB drive "to_upgrade" 2.244
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.465
Then the running Tails is installed on USB drive "to_upgrade" 15.389
And I unplug USB drive "to_upgrade" 0.156
And I unplug USB drive "__internal" 0.143
After features/support/hooks.rb:331 2.041
After features/support/hooks.rb:100 0.000
Tags: @product
1:6.166
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.890
Then all tps features from the old Tails version are active 0.924
And Tails is running from USB drive "to_upgrade" 0.276
And the boot device has safe access rights 2.288
And the expected persistent files created with the old Tails version are present in the filesystem 1.035
And all persistent directories from the old Tails version have safe access rights 1.672
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.019
Tags: @product @automatic_upgrade
4:20.067
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.108
And no SquashFS delta is installed 0.079
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.284
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.218
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.336
When the network is plugged 0.014
And Tor is ready 20.634
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.342
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.259
Given I shutdown Tails and wait for the computer to power off 18.566
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.458
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.157
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.074
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.220
When the network is plugged 0.017
And Tor is ready 21.349
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.386
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.812
Given I shutdown Tails and wait for the computer to power off 7.880
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:11.076
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.173
And the file system changes introduced in version 6.3~testoverlayfs are present 0.359
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.231
When the network is plugged 0.017
And Tor is ready 21.116
Then the Upgrader considers the system as up-to-date 0.094
# 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.755
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.395
After features/support/hooks.rb:331 0.871
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
25.090
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.670
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
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.014
And Tor is ready 16.692
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.401
After features/support/hooks.rb:331 0.897
After features/support/hooks.rb:100 0.000