Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 35 21 May 2026, 14:12

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:53.181 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.702
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.094
And I create a 7200 MiB disk named "old" 0.012
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.927
When I start Tails from USB drive "old" with network unplugged 1:0.727
Then the boot device has safe access rights 3.184
And Tails is running from USB drive "old" 0.281
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 3.445
After features/support/hooks.rb:104 0.066
Tags: @product
1:30.899
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 55.843
Then Tails is running from USB drive "old" 0.311
And I create a persistent partition 25.508
And I take note of which tps features are available 0.378
Then a Tails persistence partition exists on USB drive "old" 0.606
And I shutdown Tails and wait for the computer to power off 8.175
After features/support/hooks.rb:335 0.601
After features/support/hooks.rb:104 0.011
Tags: @product
1:26.700
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given a computer 0.112
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.202
Then Tails is running from USB drive "old" 0.267
And all tps features are active 1.214
When I write some files expected to persist 1.493
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.196
And all persistence configuration files have safe access rights 0.364
And all persistent directories from the old Tails version have safe access rights 2.019
And I take note of which tps features are available 0.145
And I shutdown Tails and wait for the computer to power off 4.011
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.671
After features/support/hooks.rb:335 0.151
After features/support/hooks.rb:104 0.008
Tags: @product
2:15.521
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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.905
And I log in to a new session 13.995
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.854
And I plug USB drive "to_upgrade" 2.295
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.425
Then the running Tails is installed on USB drive "to_upgrade" 16.768
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.333
After features/support/hooks.rb:104 0.000
Tags: @product
1:12.078
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.102
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.561
Then all tps features from the old Tails version are active 1.092
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.660
And the expected persistent files created with the old Tails version are present in the filesystem 1.243
And all persistent directories from the old Tails version have safe access rights 2.178
After features/support/hooks.rb:335 0.699
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:47.118
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.317
And no SquashFS delta is installed 0.082
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.229
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.289
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.399
When the network is plugged 0.015
And Tor is ready 13.482
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.363
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.256
Given I shutdown Tails and wait for the computer to power off 9.669
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.695
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.161
And the file system changes introduced in version 6.2~testoverlayfs are present 0.233
And only the 6.2~testoverlayfs SquashFS delta is installed 0.068
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.156
# 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.227
When the network is plugged 0.015
And Tor is ready 10.856
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.841
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.638
Given I shutdown Tails and wait for the computer to power off 8.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.747
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 1.261
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
And only the 6.3~testoverlayfs SquashFS delta is installed 0.055
# 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.135
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.185
When the network is plugged 0.019
And Tor is ready 9.968
Then the Upgrader considers the system as up-to-date 10.682
# 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.805
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.372
After features/support/hooks.rb:335 0.909
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.160
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.157
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.058
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.024
And Tor is ready 10.609
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.031
After features/support/hooks.rb:335 0.619
After features/support/hooks.rb:104 0.000