Project Number Date
test_Tails_ISO_devel 4185 23 Jan 2026, 08:49

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:56.017 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:14.350
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.071
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 14.558
When I start Tails from USB drive "old" with network unplugged 55.431
Then the boot device has safe access rights 2.558
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.210
And I unplug USB drive "old" 0.158
After features/support/hooks.rb:331 3.783
After features/support/hooks.rb:100 0.008
Tags: @product
1:33.161
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 56.652
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 26.267
And I take note of which tps features are available 0.978
Then a Tails persistence partition exists on USB drive "old" 0.686
And I shutdown Tails and wait for the computer to power off 8.244
After features/support/hooks.rb:331 0.240
After features/support/hooks.rb:100 0.006
Tags: @product
1:32.676
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.798
Then Tails is running from USB drive "old" 0.295
And all tps features are active 1.269
When I write some files expected to persist 1.408
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.183
And all persistence configuration files have safe access rights 0.344
And all persistent directories from the old Tails version have safe access rights 2.681
And I take note of which tps features are available 0.153
And I shutdown Tails and wait for the computer to power off 8.551
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.933
After features/support/hooks.rb:331 0.235
After features/support/hooks.rb:100 0.010
Tags: @product
2:14.949
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.692
And I log in to a new session 11.841
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.136
And I plug USB drive "to_upgrade" 2.254
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.931
Then the running Tails is installed on USB drive "to_upgrade" 16.783
And I unplug USB drive "to_upgrade" 0.155
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:331 2.742
After features/support/hooks.rb:100 0.000
Tags: @product
1:17.609
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.298
Then all tps features from the old Tails version are active 1.067
And Tails is running from USB drive "to_upgrade" 0.236
And the boot device has safe access rights 2.720
And the expected persistent files created with the old Tails version are present in the filesystem 1.227
And all persistent directories from the old Tails version have safe access rights 1.979
After features/support/hooks.rb:331 0.597
After features/support/hooks.rb:100 0.042
Tags: @product @automatic_upgrade
3:43.500
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.183
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.219
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.235
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.032
And Tor is ready 13.187
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.506
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.978
Given I shutdown Tails and wait for the computer to power off 10.035
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.260
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.226
And the file system changes introduced in version 6.2~testoverlayfs are present 0.217
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.141
# 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.210
When the network is plugged 0.016
And Tor is ready 12.739
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.431
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.899
Given I shutdown Tails and wait for the computer to power off 8.151
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.926
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.362
And the file system changes introduced in version 6.3~testoverlayfs are present 0.371
And only the 6.3~testoverlayfs SquashFS delta is installed 0.071
# 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.140
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.265
When the network is plugged 0.020
And Tor is ready 11.443
Then the Upgrader considers the system as up-to-date 0.153
# 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 5.101
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.443
After features/support/hooks.rb:331 1.010
After features/support/hooks.rb:100 0.012
Tags: @product @automatic_upgrade
19.769
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.877
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.185
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.165
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.436
After features/support/hooks.rb:331 1.103
After features/support/hooks.rb:100 0.000