Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Complete Test Coverage and Add Coverage Reporting for Identity Service #214

Open
6 of 10 tasks
lakshayman opened this issue May 31, 2024 · 0 comments
Open
6 of 10 tasks

Comments

@lakshayman
Copy link
Collaborator

lakshayman commented May 31, 2024

Issue Description

Currently, our identity service has a test setup in place, but the tests are only partially written for the verify and health functions. We need to extend the test coverage to include the call-profile, call-profiles, and health-check functions. Additionally, we need to implement a method to measure and report the test coverage.

Expected Behavior

When this issue is resolved:

  • Comprehensive test coverage will be in place for the call-profile, call-profiles, and health-check functions.
  • A test coverage tool will be implemented to measure and report the coverage of our tests.

Current Behavior

  • Tests are only partially written for the verify and health functions.
  • No tests are currently written for the call-profile, call-profiles, and health-check functions.
  • There is no existing mechanism to measure and report test coverage.

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Inspect the existing test suite for the identity service.
  2. Note the presence of tests for the verify and health functions.
  3. Observe the absence of tests for the call-profile, call-profiles, and health-check functions.
  4. Verify the lack of a test coverage reporting mechanism.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant