ilpanich / axiam-rust-sdk / 30030932223

94%

push

github

test(coverage): Rust SDK 89.3% → ≥92% + ratchet gate 89→90 (Phase C) (#26)

* test(rest/auth): cover deser_err, unresolved tenant/org, missing cookie, no-jti logout

Phase C (C1): src/rest/auth.rs was at 88.18% line coverage (35 missed).
Extends tests/rest_auth_more_test.rs with the branches the existing
wiremock-based lifecycle/more suites never reached:

- login()/verify_mfa()/refresh() malformed-200/202-body -> deser_err
  (previously never exercised for the auth endpoints at all, only for
  rest/authz.rs).
- refresh()'s "tenant_id could not be resolved" and "org_id could not be
  resolved" guards, via a token whose claims are crafted to leave one
  resolved and the other not.
- refresh()'s post-success "refresh response did not set axiam_access"
  guard, via a rotated response that actively expires the cookie
  (Max-Age=0) rather than omitting Set-Cookie (which would leave the
  jar's pre-existing login cookie untouched and not exercise this path).
- logout()'s "access token has no session id (jti)" guard.

rest/auth.rs line coverage: 88.18% -> 93.24%.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01MbKy7FMMeAAXSoAzvMKKNR

* test(token/jwks): cover forced-refetch throttle, transport failure, sig/claim errors

Phase C (C2): src/token/jwks.rs was at 87.94% line coverage (24 missed).

tests/jwks_fetch_and_refetch_test.rs:
- force_refetch_if_allowed's throttle branch: a second unknown-kid verify()
  immediately following the first forced refetch must reuse the cached
  JWKS rather than firing a second network fetch (previously only the
  "no prior forced refetch" allow-arm was exercised).
- fetch_and_cache's transport-failure branch (connection refused),
  distinct from the already-covered non-2xx-status branch.
- JwksVerifier::new's own `base_url.join(JWKS_PATH)` error branch, via a
  cannot-be-a-base URL.

tests/jwks_verify_branches_test.rs:
- ErrorKind::InvalidSignature (a token signed with t... (continued)

11 of 0 new or added lines in 0 files covered. (NaN%)

2175 of 2319 relevant lines covered (93.79%)

10.04 hits per line