Clause coverage highlighting for multiple groups

[elsaperelli]

Summary

Before, the coverage highlighting only happened for one measure group. Now, it calculates the coverage for all patients for each individual group.

New behavior

generateClauseCoverageHTML now returns a lookup object where the key is the groupId and the value is the clause coverage html for that group. There is an additional property on the CalculationOutput interface for groupClauseCoverageHTML.

Code changes

• src/calculation/Calculator.ts- The lookup object created by generateClauseCoverageHTML is now returned as part of the CalculationOutput in the calculate function. If the debug output is enabled, an html file for the overall clause coverage html is created and contains the html for each group. In addition, an html file is created for each of the groups clause coverage html.
• src/Calculation/HTMLBuilder.ts- generateClauseCoverageHtml iterates through each execution result and adds the detailedResult to a lookup object where the key is its corresponding groupId. Then, it iterates through that lookup object and calculates the clauseCoverageHtml for each of the groups in that lookup object. The html for each group is added to another lookup object where the key is the groupId and the value is the clause coverage html for that group. That lookup object is then returned.
• src/types/Calculator.ts- The optional groupClauseCoverageHTML property was added to the CalculationOutput interface.
• test/HTMLGenerator.test.ts- Tests were changed to reflect the changes to the return type of generateClauseCoverageHTML.
• test/fixtures/html/SimpleCoverageAnnotation.html- This file was modified to include the group name.
• test/fixtures/html/SimpleCoverageAnnotation2.html- This file was added for the unit test that tests generateClauseCoverageHTML on multiple groups.

Testing guidance

1. npm run check to ensure that unit tests pass and there are no prettier or lint errors/warnings.
2. Using the files attached below, run the following command: npm run cli -- detailed -m <path-to-measure-bundle.json> -p <path-to-pt1.json> <path-to-pt2.json> -o --debug
3. Look at the html files in the debug directory. There should be 4 files: two for each group that includes that group's clause coverage and two for each group that includes that group's measure highlighting.
4. Let me know if you have any questions and more importantly if you have any suggestions for additional unit tests or testing methods.

coverage-test-case.zip

[github-actions[bot]]

Coverage report

St.:grey_question:	Category	Percentage	Covered / Total
🟢	Statements	85.71% (-0.08% 🔻)	1938/2261
🟡	Branches	73.75% (-0.13% 🔻)	1711/2320
🟢	Functions	88.72% (-0.23% 🔻)	346/390
🟢	Lines	85.96% (-0.07% 🔻)	1868/2173

Show files with reduced coverage 🔻

|

St.^{:grey_question:}

| File | Statements | Branches | Functions | Lines | | :----------------------------------------------------------------------------------------------------------------------------------------------------: | :------------------------------------------------------------------- | :------------------------------------------------------------- | :------------------------------------------------------------- | :------------------------------------------------------------- | :------------------------------------------------------------- | | 🟢 |

`...` / HTMLBuilder.ts

|

92.66% (-1.78% 🔻)

|

67.57% (-8.29% 🔻)

|

88.24% (-2.67% 🔻)

|

92.71% (-1.92% 🔻)

|

Test suite run success

349 tests passing in 28 suites.

Report generated by 🧪jest coverage report action from ccdb05a13c41a2518fcc053464371a63ed6aba61