test(compliance): end-to-end compliance lifecycle integration test - #283
Merged
Conversation
… test Prove the compliance web layer end to end: a full-context Spring Boot test drives a case from open through claim to resolved over HTTP against real Postgres, checks that re-resolving a terminal case returns 409, that opening with only the read scope is forbidden, that the OpenAPI document lists both the KYC and case endpoints, and that the health endpoint is reachable without a token. The web layer itself (security, RFC 7807, observability, OpenAPI) shipped in earlier slices; this closes the consolidation by exercising it as a whole. Closes #270
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Final ticketed E-04 slice (#270) - consolidation proven end-to-end.
What #270 adds
ComplianceLifecycleIT(@SpringBootTest + Testcontainers Postgres + MockMvc, mirroring the merged KycApiContextIT full-context setup): drives a case open -> claim -> resolve over HTTP against real Postgres, asserts double-resolve -> 409 (RFC7807 conflict end-to-end), 403 on open with only the read scope (paired with the 201 write path = non-vacuous deny/allow), the OpenAPI doc lists both/v1/kyc/sessionsand/v1/compliance/cases, and/actuator/healthis reachable without a token (permitAll + observability baseline).Honest scope - AC mapping (most production work shipped earlier)
Gate chain
spring.kafka.listener.auto-startup=false; exact scope consts; AC->prior-PR mapping - applied).Local compile/detekt/spotless green; the IT runs on CI (Postgres). With this, all ticketed E-04 slices (F-04.1 Compliance module + domain #261-F-04.10 Compliance REST security + OpenAPI + lifecycle ITs #270) are done.
Closes #270