Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 72 24 Jun 2026, 14:22

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:35.470 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:7.293
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.046
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.041
When I start Tails from USB drive "old" with network unplugged 49.974
Then the boot device has safe access rights 2.512
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.069
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.217
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:339 1.415
After features/support/hooks.rb:108 0.008
Tags: @product
1:27.579
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 53.526
Then Tails is running from USB drive "old" 0.248
And I create a persistent partition 24.920
And I take note of which tps features are available 4.024
Then a Tails persistence partition exists on USB drive "old" 0.557
And I shutdown Tails and wait for the computer to power off 4.249
After features/support/hooks.rb:339 0.326
After features/support/hooks.rb:108 0.006
Tags: @product
1:33.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.696
Then Tails is running from USB drive "old" 0.219
And all tps features are active 4.378
When I write some files expected to persist 1.228
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.189
And all persistence configuration files have safe access rights 0.323
And all persistent directories from the old Tails version have safe access rights 1.897
And I take note of which tps features are available 3.779
And I shutdown Tails and wait for the computer to power off 8.219
# 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" 11.685
After features/support/hooks.rb:339 0.186
After features/support/hooks.rb:108 0.006
Tags: @product
2:8.366
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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 7.920
And I log in to a new session 11.491
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.782
And I plug USB drive "to_upgrade" 2.213
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.243
Then the running Tails is installed on USB drive "to_upgrade" 14.426
And I unplug USB drive "to_upgrade" 0.158
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 2.071
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.346
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.440
Then all tps features from the old Tails version are active 1.031
And Tails is running from USB drive "to_upgrade" 0.247
And the boot device has safe access rights 2.387
And the expected persistent files created with the old Tails version are present in the filesystem 1.264
And all persistent directories from the old Tails version have safe access rights 1.922
After features/support/hooks.rb:339 0.889
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:47.440
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.971
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.213
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.215
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.014
And Tor is ready 12.445
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.531
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.366
Given I shutdown Tails and wait for the computer to power off 9.311
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.346
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.783
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.118
# 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.214
When the network is plugged 0.017
And Tor is ready 11.062
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.867
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.108
Given I shutdown Tails and wait for the computer to power off 7.834
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.147
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.885
And the file system changes introduced in version 6.3~testoverlayfs are present 0.319
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.124
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.252
When the network is plugged 0.013
And Tor is ready 10.953
Then the Upgrader considers the system as up-to-date 10.502
# 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 3.742
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.331
After features/support/hooks.rb:339 1.077
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
20.740
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.062
And the signing key used by the Upgrader is outdated 0.067
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 10.157
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.937
After features/support/hooks.rb:339 0.996
After features/support/hooks.rb:108 0.000