This Issue is a duplicate of UCO Issue 488, filed because UCO Issue 488 left handling typo review within CASE as out-of-scope.
Requirements
Requirement 1
Requirement 1 from UCO Issue 488 should carry over to CASE.
Risk / Benefit analysis
Benefits
Aligns testing practices between UCO and CASE on design-vocabulary typo detection.
Risks
UCO Issue 488 noted it was leaving making an exportable pytest function as out-of-scope. This Issue does not suggest anything more sophisticated than copying and pasting a pytest function, which creates a potential point of code-drift.
Competencies demonstrated
Competencies of UCO Issue 488 apply to CASE as well.
Fortunately, no typos were found, and the non-existent concept owl:ontologyIRI is already addressed in PR 118.
Solution suggestion
Start implementation from the branch in CASE PR 118.
Copy the pytest function test_rdf_design_vocabularies_defined from UCO.
Copy the pytest unit test call logistics from UCO.
Background
This Issue is a duplicate of UCO Issue 488, filed because UCO Issue 488 left handling typo review within CASE as out-of-scope.
Requirements
Requirement 1
Requirement 1 from UCO Issue 488 should carry over to CASE.
Risk / Benefit analysis
Benefits
Risks
pytestfunction as out-of-scope. This Issue does not suggest anything more sophisticated than copying and pasting apytestfunction, which creates a potential point of code-drift.Competencies demonstrated
Competencies of UCO Issue 488 apply to CASE as well.
Fortunately, no typos were found, and the non-existent concept
owl:ontologyIRIis already addressed in PR 118.Solution suggestion
pytestfunctiontest_rdf_design_vocabularies_definedfrom UCO.pytestunit test call logistics from UCO.Coordination
develop