Project Number Date
test_Tails_ISO_21651-persist-gnome-software-dconf-state 1 22 Jul 2026, 18:36

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:0.858 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:14.412
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.048
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.424
When I start Tails from USB drive "old" with network unplugged 56.364
Then the boot device has safe access rights 2.779
And Tails is running from USB drive "old" 0.312
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.216
And I unplug USB drive "old" 0.142
After features/support/hooks.rb:339 1.483
After features/support/hooks.rb:108 0.009
Tags: @product
1:33.204
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.141
And I start Tails from USB drive "old" with network unplugged and I login 55.560
Then Tails is running from USB drive "old" 0.296
And I create a persistent partition 25.249
And I take note of which tps features are available 4.595
Then a Tails persistence partition exists on USB drive "old" 0.548
And I shutdown Tails and wait for the computer to power off 6.811
After features/support/hooks.rb:339 0.120
After features/support/hooks.rb:108 0.006
Tags: @product
1:35.743
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.051
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.865
Then Tails is running from USB drive "old" 0.224
And all tps features are active 5.602
When I write some files expected to persist 1.417
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.216
And all persistence configuration files have safe access rights 0.316
And all persistent directories from the old Tails version have safe access rights 2.045
And I take note of which tps features are available 4.057
And I shutdown Tails and wait for the computer to power off 4.306
# 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.639
After features/support/hooks.rb:339 0.622
After features/support/hooks.rb:108 0.007
Tags: @product
2:13.037
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.932
And I log in to a new session 13.467
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.857
And I plug USB drive "to_upgrade" 2.226
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.273
Then the running Tails is installed on USB drive "to_upgrade" 15.991
And I unplug USB drive "to_upgrade" 0.136
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:339 2.772
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.193
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.060
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.025
Then all tps features from the old Tails version are active 0.946
And Tails is running from USB drive "to_upgrade" 0.234
And the boot device has safe access rights 2.588
And the expected persistent files created with the old Tails version are present in the filesystem 1.104
And all persistent directories from the old Tails version have safe access rights 2.233
After features/support/hooks.rb:339 0.765
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:49.411
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.239
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.279
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.431
When the network is plugged 0.031
And Tor is ready 13.612
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.113
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.984
Given I shutdown Tails and wait for the computer to power off 5.435
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.789
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 5.461
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.072
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.133
# 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.196
When the network is plugged 0.015
And Tor is ready 10.196
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.596
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.500
Given I shutdown Tails and wait for the computer to power off 4.322
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.626
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.878
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.163
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.267
When the network is plugged 0.013
And Tor is ready 9.671
Then the Upgrader considers the system as up-to-date 10.683
# 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.313
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.339
After features/support/hooks.rb:339 1.022
After features/support/hooks.rb:108 0.014
Tags: @product @automatic_upgrade
20.855
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.364
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.040
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.685
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.462
After features/support/hooks.rb:339 0.880
After features/support/hooks.rb:108 0.000