cqframework / cqframework/vscode-cql
Warning for test cases with bad references
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Description
Test cases that use references need validation. The Java CQL engine honors references, but there is no indication within VS that there is a problem with the references.
The issue was found when running test cases from MADie. MADie, and the underlying fqm-execution engine, don't check references. In DQM 2025 there were test cases with bad references, so the VSCode results didn't match MADie.
Add a check on test case references.
Contributor guide
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
No file or test is named. Start by locating the VS Code test-case execution and results entry points, then compare their reference handling with the Java CQL engine, MADie, and fqm-execution behavior; done means bad references produce a visible warning and results no longer diverge.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100