Skip to content

Refactor: test_jwt.py fully modularized with mock jwt.encode + expiry simulation #1726

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

Open
wants to merge 17 commits into
base: main
Choose a base branch
from

Conversation

cureprotocols
Copy link

This PR introduces a full refactor of tests/test_jwt.py with the following enhancements:

✅ Split into clean, modular sections:

  • Section 1: Core claim validation (sub, aud, iat)
  • Section 2: JWT header logic and parametrize coverage
  • Section 3: Exception handling for invalid signer & payloads
  • Section 4: Time-based claim handling using exp, nbf, iat with freezegun

✅ Introduced smart dummy_encode() to simulate jwt.encode() behavior

  • Simulates errors for missing 'alg'
  • Simulates exp and nbf time validation
  • Raises runtime and type errors for edge cases

✅ All 15 tests pass using local fixtures and mocks (no external crypto or network dependency)

This refactor improves test clarity, modularity, and CI reliability.
Next steps can include real JWT plug-in, test_identity_pool.py refactor, or CI wiring.


@cureprotocols cureprotocols requested review from a team as code owners April 4, 2025 16:38
Copy link

google-cla bot commented Apr 4, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

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

Successfully merging this pull request may close these issues.

1 participant