Project Number Date
test_Tails_ISO_devel 4253 25 Feb 2026, 11:38

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 12:43.208 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:6.698
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.605
When I start Tails from USB drive "old" with network unplugged 48.466
Then the boot device has safe access rights 2.845
And Tails is running from USB drive "old" 0.260
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.054
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:331 1.368
After features/support/hooks.rb:100 0.006
Tags: @product
1:29.958
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login 55.218
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 24.975
And I take note of which tps features are available 0.668
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 8.198
After features/support/hooks.rb:331 0.418
After features/support/hooks.rb:100 0.006
Tags: @product
1:24.346
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 "old" with network unplugged and I login with persistence enabled 1:2.186
Then Tails is running from USB drive "old" 0.249
And all tps features are active 1.194
When I write some files expected to persist 1.264
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.266
And all persistent directories from the old Tails version have safe access rights 1.947
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 4.310
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 12.560
After features/support/hooks.rb:331 0.482
After features/support/hooks.rb:100 0.027
Tags: @product
2:14.618
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 without a persistent partition and stopped at Tails Greeter's login screen 8.339
And I log in to a new session 13.055
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.768
And I plug USB drive "to_upgrade" 2.200
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.149
Then the running Tails is installed on USB drive "to_upgrade" 16.831
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:331 4.437
After features/support/hooks.rb:100 0.000
Tags: @product
1:12.248
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Given a computer 0.046
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.493
Then all tps features from the old Tails version are active 0.918
And Tails is running from USB drive "to_upgrade" 0.229
And the boot device has safe access rights 2.544
And the expected persistent files created with the old Tails version are present in the filesystem 1.145
And all persistent directories from the old Tails version have safe access rights 1.870
After features/support/hooks.rb:331 0.620
After features/support/hooks.rb:100 0.049
Tags: @product @automatic_upgrade
4:47.155
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.689
And no SquashFS delta is installed 0.153
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.095
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.378
When the network is plugged 0.014
And Tor is ready 26.561
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.379
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.567
Given I shutdown Tails and wait for the computer to power off 20.296
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:15.287
Then Tails is running version 6.2~testoverlayfs 0.026
And all tps features are active 1.215
And the file system changes introduced in version 6.2~testoverlayfs are present 0.257
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.157
# 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.330
When the network is plugged 0.076
And Tor is ready 21.079
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.437
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.707
Given I shutdown Tails and wait for the computer to power off 17.583
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.296
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.167
And the file system changes introduced in version 6.3~testoverlayfs are present 0.408
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.259
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.244
When the network is plugged 0.017
And Tor is ready 21.531
Then the Upgrader considers the system as up-to-date 0.105
# 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.804
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:331 1.036
After features/support/hooks.rb:100 0.013
Tags: @product @automatic_upgrade
28.182
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 7.675
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.051
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 19.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.374
After features/support/hooks.rb:331 0.619
After features/support/hooks.rb:100 0.000