In the case of a package harvested from GOKb/external source lacking key information about the package, log the issue and fail gracefully
Description
defines
Checklist
hideTestRail: Results
Activity
Show:

Owen Stephens December 1, 2021 at 2:28 PM
Yes - those are fine for me
Thanks

Peter Böhm December 1, 2021 at 9:34 AM
: Are these log messages sufficient in terms of the identifier?
Done
Details
Details
Components
Assignee

Reporter

Priority
Sprint
None
Development Team
Bienenvolk
Release
Lotus R1 2022
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 27, 2021 at 2:28 PM
Updated December 15, 2021 at 10:07 AM
Resolved December 9, 2021 at 5:44 PM
TestRail: Cases
TestRail: Runs
Purpose/Overview:
When harvesting a package from GOKb then it can fail if key information is lacking in the GOKb XML being processed for the package. Specifically:
package_record.name?.text() [used to populate the package name]
package_record.shortcode?.text() [used to populate the packageSlug / package reference]
In the cases where this information is missing for the package, the package should be skipped and the information recorded in the info log
Scenario 1:
Given: a package in the GOKb XML being processed by the adapter
When: the package lacks a name
Then: the package should be skipped and an info log entry created indicating that the package has been skipped with a reference to the GOKb package.id
Scenario 2:
Given: a package in the GOKb XML being processed by the adapter
When: the package lacks a shortcode
Then: the package should be skipped and an info log entry created indicating that the package has been skipped with a reference to the GOKb package.name or package.id
example GOKb package xml: