cqframework / cqframework/cql-tests
Annotating Tests w/ Translation Errors
@raleigh-g-thompson is already working on this.
Since Oct 1, 2025.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 8
- Avg merge
- 12d 5h
- Merged PRs (30d)
- 2
Description
There are several tests that currently do not translate (intentionally or unintentionally).
- Some tests, like CqlTypesTest.Time.TimeUpperBoundHours, are marked with
invalid="semantic"and an XML comment with the translation error. - Other tests, like CqlDateTimeOperatorsTest.Uncertainty tests.TimeDurationBetweenHourDiffPrecision, are marked with
invalid="true"and an XML comment with the translation error. - Still other tests, like CqlIntervalOperatorsTest.Expand.ExpandPer1, do not populate the
invalidparameter at all but do have an XML comment with the translation error.
I think it would be good to have some consistency here so that implementations of this testing framework know how to handle these. Ideally, implementations shouldn't need to process and parse XML comments to know that a translation error is expected. While using invalid="true" helps some, it is still problematic since it is used for both translation errors and run-time errors.
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.
Assessment
This issue has not been assessed yet.