Project Number Date
test_Tails_ISO_devel 4163 13 Jan 2026, 22:32

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:18.832 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.286
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.063
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.490
When I start Tails from USB drive "old" with network unplugged 47.059
Then the boot device has safe access rights 2.929
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.072
And udev-watchdog is monitoring the correct device 0.206
And I unplug USB drive "old" 0.131
After features/support/hooks.rb:331 3.794
After features/support/hooks.rb:100 0.006
Tags: @product
1:27.345
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 53.224
Then Tails is running from USB drive "old" 0.310
And I create a persistent partition 24.395
And I take note of which tps features are available 0.607
Then a Tails persistence partition exists on USB drive "old" 0.595
And I shutdown Tails and wait for the computer to power off 8.154
After features/support/hooks.rb:331 0.534
After features/support/hooks.rb:100 0.007
Tags: @product
1:27.169
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.889
Then Tails is running from USB drive "old" 0.285
And all tps features are active 1.252
When I write some files expected to persist 1.334
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.172
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 2.047
And I take note of which tps features are available 0.138
And I shutdown Tails and wait for the computer to power off 7.839
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.849
After features/support/hooks.rb:331 0.193
After features/support/hooks.rb:100 0.007
Tags: @product
2:12.245
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 8.331
And I log in to a new session 11.365
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.848
And I plug USB drive "to_upgrade" 2.228
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.294
Then the running Tails is installed on USB drive "to_upgrade" 15.806
And I unplug USB drive "to_upgrade" 0.164
And I unplug USB drive "__internal" 0.205
After features/support/hooks.rb:331 4.095
After features/support/hooks.rb:100 0.000
Tags: @product
1:9.327
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.088
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.711
Then all tps features from the old Tails version are active 0.882
And Tails is running from USB drive "to_upgrade" 0.297
And the boot device has safe access rights 2.541
And the expected persistent files created with the old Tails version are present in the filesystem 1.083
And all persistent directories from the old Tails version have safe access rights 1.722
After features/support/hooks.rb:331 0.935
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:37.835
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.265
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.071
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.437
When the network is plugged 0.019
And Tor is ready 13.267
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.768
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.126
Given I shutdown Tails and wait for the computer to power off 6.850
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.176
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.138
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.041
# 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.236
When the network is plugged 0.018
And Tor is ready 11.552
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.532
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.720
Given I shutdown Tails and wait for the computer to power off 8.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.371
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.172
And the file system changes introduced in version 6.3~testoverlayfs are present 0.361
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.137
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.196
When the network is plugged 0.014
And Tor is ready 10.693
Then the Upgrader considers the system as up-to-date 10.637
# 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.436
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 0.619
After features/support/hooks.rb:100 0.010
Tags: @product @automatic_upgrade
19.622
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.807
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.049
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.767
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.733
After features/support/hooks.rb:331 0.591
After features/support/hooks.rb:100 0.000