Project Number Date
test_Tails_ISO_devel 4220 09 Feb 2026, 18:33

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.343 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:19.612
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.041
And I write an old version of the Tails USB image to disk "old" 13.657
When I start Tails from USB drive "old" with network unplugged 1:0.751
Then the boot device has safe access rights 3.330
And Tails is running from USB drive "old" 0.248
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.209
And I unplug USB drive "old" 0.209
After features/support/hooks.rb:331 3.533
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.517
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.001
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login 55.152
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 24.422
And I take note of which tps features are available 0.785
Then a Tails persistence partition exists on USB drive "old" 0.569
And I shutdown Tails and wait for the computer to power off 8.229
After features/support/hooks.rb:331 0.404
After features/support/hooks.rb:100 0.014
Tags: @product
1:29.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.057
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.727
Then Tails is running from USB drive "old" 0.738
And all tps features are active 1.410
When I write some files expected to persist 1.371
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.149
And all persistence configuration files have safe access rights 0.368
And all persistent directories from the old Tails version have safe access rights 2.046
And I take note of which tps features are available 0.182
And I shutdown Tails and wait for the computer to power off 7.883
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.397
After features/support/hooks.rb:331 0.556
After features/support/hooks.rb:100 0.006
Tags: @product
2:12.260
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.658
And I log in to a new session 11.772
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.824
And I plug USB drive "to_upgrade" 2.248
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.137
Then the running Tails is installed on USB drive "to_upgrade" 15.352
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 3.395
After features/support/hooks.rb:100 0.000
Tags: @product
1:11.676
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.332
Then all tps features from the old Tails version are active 1.034
And Tails is running from USB drive "to_upgrade" 0.307
And the boot device has safe access rights 2.979
And the expected persistent files created with the old Tails version are present in the filesystem 1.114
And all persistent directories from the old Tails version have safe access rights 1.854
After features/support/hooks.rb:331 0.531
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
3:51.048
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.960
And no SquashFS delta is installed 0.067
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.254
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.240
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.481
When the network is plugged 0.015
And Tor is ready 13.882
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.246
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.072
Given I shutdown Tails and wait for the computer to power off 9.559
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.655
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 2.173
And the file system changes introduced in version 6.2~testoverlayfs are present 0.272
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.158
# 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.180
When the network is plugged 0.017
And Tor is ready 12.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.042
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.143
Given I shutdown Tails and wait for the computer to power off 7.963
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.392
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 1.264
And the file system changes introduced in version 6.3~testoverlayfs are present 0.306
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.172
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.283
When the network is plugged 0.015
And Tor is ready 11.549
Then the Upgrader considers the system as up-to-date 10.778
# 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.916
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.371
After features/support/hooks.rb:331 0.907
After features/support/hooks.rb:100 0.034
Tags: @product @automatic_upgrade
20.894
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.572
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.060
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.140
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.811
After features/support/hooks.rb:331 0.889
After features/support/hooks.rb:100 0.000