asgardeo / asgardeo/javascript

chore: add unit test coverage for untested code paths in `@asgardeo/react` SDK

Offen
#167 9 Kommentare 0 Reaktionen 1 zugewiesene Person Beansprucht von @Kavidu23 Auf GitHub ansehen
@asgardeo/react Complexity/Medium Credits/30 Hacktoberfest Type/Improvement Type/Task
Vorherrschende Sprache
TypeScript
Sterne
18
Forks
67
Ø Merge
4 Std. 6 Min.
Gemergte PRs (30 T.)
13

Beschreibung

### Current Limitation

Some code paths and edge cases in @asgardeo/react are not covered by unit tests, leading to reduced confidence in code changes, potential bugs, and lower test coverage.

- Reduced confidence in code changes and refactoring
- Potential undetected bugs in less common scenarios
- Lower overall test coverage metrics
- Increased manual testing effort
- Difficulty in maintaining code quality over time

Without adequate unit tests, the codebase may contain:

- Functions or methods that are not validated for all input variations
- Edge cases that may break silently
- Logic errors that are only caught in integration or production environments

### Suggested Improvement

Identify and add unit tests for untested code paths and edge cases in @asgardeo/react. Improve test coverage and reliability.

## Implementation Plan

1. Review the latest code coverage to identify untested lines/branches.
2. Select a function, method, or component that lacks test coverage.
3. Write a new unit test that:
- Covers normal, boundary, and invalid input cases
- Asserts correct output and expected error handling
4. Run the test suite to confirm the new test is effective and passes.
5. Update documentation or test coverage badges as necessary.

**References:**
- https://vitest.dev/
- [Improving test coverage](https://blog.codecov.io/how-to-improve-code-coverage-ec7d5c5e1236/)

### Please select the package issue is related to

@asgardeo/express

### Version

Current

### Reporter Checklist

- [x] I have searched the existing issues and this is not a duplicate.
- [x] I have provided all the necessary information.
- [x] I have verified the improvement is not available in the latest version of the package.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.