Add unit test and CI
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
After reviewing the issues caught in the spdx-spec CI runs of PySHACL, we could greatly shorting the error discovery time if we run something similar as a CI in the spec-parser itself.
The quickest implementation would be to basically copy the validation portions of the CI and create a test target with the example file being tested in the spec-parser.
A better implementation would be to have a richer example file with all properties, profiles and fields present (similar to the example files in the SPDX 2 version of spec).
A middle ground would be to translate the SPDX 2 example to SPDX 3.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the validation portions of the PySHACL spdx-spec CI and the existing spec-parser example file first. Define which example and validation scope to use, then confirm that the spec-parser CI runs the new test and reports validation failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100