Stream: cql
Topic: code coverage
Kevin Olbrich (Jan 30 2018 at 20:32):
@Bryn Rhodes are there some code coverage metrics for the tests for CQL? Or something like https://github.com/ruby/spec for CQL? I.e., something concrete to indicate how well tested it is.
Bryn Rhodes (Jan 30 2018 at 21:57):
We have regression suites defined in both the CQL-to-ELM translator and the CQL Engine implementations. Coverage metrics would be good though, I'll look at determining coverage.
Kevin Olbrich (Jan 30 2018 at 22:06):
It might be helpful to have a series of tests defined in CQL that are then serialized to ELM. Then I could use those ELM files as a test-driven development tool to build an execution engine for ruby.
Chris Moesel (Feb 12 2018 at 21:02):
@Kevin Olbrich -- You might want to look at the test suite in the CoffeeScript execution engine. We wrote a series of tests in CQL, and then have a process that converts them into data.coffee files that just contain a reference to the resulting ELM JSON. Eventually I'll probably convert this over to just use straight up JSON ELM (e.g., data.elm.json instead of data.coffee) -- but this may still at least be a start at being helpful? Note that the actual assertions, however, are still in test.coffee files. https://github.com/cqframework/clinical_quality_language/tree/master/Src/coffeescript/cql-execution/test/elm
Last updated: Apr 12 2022 at 19:14 UTC
