9 implement test coverage verification in cicd fail coverage

[cstroliadavis]

Issue No:

Replace this text with the issue number in GH-### format, where ### refers to the related github issue.

Issue Type:

• [ ] Architecture (ensure that the architecture lead is included in the reviewers
• [ ] Bug
• [ ] Chore
• [ ] Clean-up
• [ ] DevOps (ensure that the devops lead is included in the reviewers)
• [ ] Documentation
• [ ] Feature Request (ensure that the team lead and architecture lead are included in reviewers if this involves any core functionality changes)

Description

Please include a summary of the change and which issue is fixed. Include relevant motivation and context. List any dependencies that are required for this change.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration.

Checklist:

• [ ] This is not a code change, or my code follows the style guidelines of this project and I have run eslint
• [ ] I have performed a self-review of my own changes
• [ ] I have not added or modified any publicly available objects or methods or I have added appropriate jsdoc comments
• [ ] I did not make any abnormal changes or I have added comments describing "why" I did things differently than usual.
• [ ] This is a documentation update, or else I have made corresponding changes to the documentation
• [ ] My changes generate no new errors or warnings
• [ ] I have not added any code the requires unit test updates, or I have added unit tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes

[cstroliadavis]

This was a PR made just to check a pipeline for failures. Failures worked as expected, so closing