Project Number Date
test_Tails_ISO_21569-fix-gnome-software-notifications 1 02 Oct 2026, 17:55

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:20.976 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:9.819
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.118
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.296
When I start Tails from USB drive "old" with network unplugged 52.677
Then the boot device has safe access rights 2.046
And Tails is running from USB drive "old" 0.241
And there is no persistence partition on USB drive "old" 0.089
And process "udev-watchdog" is running 0.042
And udev-watchdog is monitoring the correct device 0.146
And I unplug USB drive "old" 0.111
After features/support/hooks.rb:339 3.773
After features/support/hooks.rb:108 0.074
Tags: @product
1:19.996
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "old" with network unplugged and I login 48.550
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 21.887
And I take note of which tps features are available 6.165
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 2.596
After features/support/hooks.rb:339 0.344
After features/support/hooks.rb:108 0.012
Tags: @product
1:34.495
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.231
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.985
Then Tails is running from USB drive "old" 0.218
And all tps features are active 7.392
When I write some files expected to persist 1.040
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.141
And all persistence configuration files have safe access rights 0.229
And all persistent directories from the old Tails version have safe access rights 1.428
And I take note of which tps features are available 6.124
And I shutdown Tails and wait for the computer to power off 4.189
# 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.513
After features/support/hooks.rb:339 0.334
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.370
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 8.615
And I log in to a new session 12.364
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.795
And I plug USB drive "to_upgrade" 2.279
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.924
Then the running Tails is installed on USB drive "to_upgrade" 19.113
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 1.891
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.175
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.109
Then all tps features from the old Tails version are active 1.128
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 2.048
And the expected persistent files created with the old Tails version are present in the filesystem 0.976
And all persistent directories from the old Tails version have safe access rights 1.626
After features/support/hooks.rb:339 0.687
After features/support/hooks.rb:108 0.005
3:34.453
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 with a persistent partition enabled and logged in 8.440
And no SquashFS delta is installed 0.064
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
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.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.339
When the network is plugged 0.028
And Tor is ready 13.240
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.332
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.349
Given I shutdown Tails and wait for the computer to power off 5.271
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.412
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.459
And the file system changes introduced in version 6.2~testoverlayfs are present 0.252
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.143
# 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.205
When the network is plugged 0.030
And Tor is ready 10.628
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.348
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.062
Given I shutdown Tails and wait for the computer to power off 4.234
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.362
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.178
And the file system changes introduced in version 6.3~testoverlayfs are present 0.383
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.184
When the network is plugged 0.022
And Tor is ready 10.244
Then the Upgrader considers the system as up-to-date 0.087
# 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.019
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:339 0.873
After features/support/hooks.rb:108 0.032
18.665
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.701
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.253
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.056
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 9.726
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.861
After features/support/hooks.rb:339 0.545
After features/support/hooks.rb:108 0.000