A test suite would help us ensure that jphyloref continues to work as expected. In particular, since the 'test' command is now being used as a part of the phyloref/curation-workflow, we should ensure that it produces output as expected by the curation workflow, and doesn't fail on malformed JSON or invalid OWL without correctly reporting issues.
If parts of jphyloref are split into separate tools (such as a dedicated testing tool and a phyloreferencing library), the test suite should be flexible enough to be easily split between these tools.
A test suite would help us ensure that jphyloref continues to work as expected. In particular, since the 'test' command is now being used as a part of the phyloref/curation-workflow, we should ensure that it produces output as expected by the curation workflow, and doesn't fail on malformed JSON or invalid OWL without correctly reporting issues.
If parts of jphyloref are split into separate tools (such as a dedicated testing tool and a phyloreferencing library), the test suite should be flexible enough to be easily split between these tools.