eho/register-referentie
1
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

S-04a · ACL integration test against real OpenZaak (Testcontainers) #46

New Issue
Closed
opened 2026-06-04 09:19:18 +00:00 by eho · 0 comments
eho commented 2026-06-04 09:19:18 +00:00
Owner
Copy Link

Split off from #5 (CLAUDE.md §13). S-04 delivered the ACL OpenZaak operation, unit tests, and a Reqnroll BDD scenario run against an in-memory stand-in for the Zaken API. This issue covers the remaining S-04 acceptance criterion:

Integration test using Testcontainers against real OpenZaak passes.

Outcome: An integration test that targets real OpenZaak and asserts OpenZaakGateway POSTs a valid, default-filled zaak (ADR-0003) and gets back a zaak URL — exercising real JWT auth and the real POST /zaken/api/v1/zaken contract, which the stubbed-HttpMessageHandler unit test cannot.

Open question (decide here): OpenZaak needs Postgres + Redis + a seeded BIG catalogus, heavy for pure Testcontainers. Options: (a) full Testcontainers graph, (b) target the already-up 'make stack-up' compose stack. Record the choice.

Out of scope: other ZGW operations, status transitions, documents.

Split off from #5 (CLAUDE.md §13). S-04 delivered the ACL OpenZaak operation, unit tests, and a Reqnroll BDD scenario run against an in-memory stand-in for the Zaken API. This issue covers the remaining S-04 acceptance criterion: > Integration test using Testcontainers against real OpenZaak passes. **Outcome:** An integration test that targets real OpenZaak and asserts OpenZaakGateway POSTs a valid, default-filled zaak (ADR-0003) and gets back a zaak URL — exercising real JWT auth and the real POST /zaken/api/v1/zaken contract, which the stubbed-HttpMessageHandler unit test cannot. **Open question (decide here):** OpenZaak needs Postgres + Redis + a seeded BIG catalogus, heavy for pure Testcontainers. Options: (a) full Testcontainers graph, (b) target the already-up 'make stack-up' compose stack. Record the choice. **Out of scope:** other ZGW operations, status transitions, documents.
eho added this to the Iteration 1 — Walking Skeleton milestone 2026-06-04 09:19:18 +00:00
eho added the type:slicearea:acl labels 2026-06-04 09:19:18 +00:00
not closed this issue 2026-06-29 10:48:01 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:acl
area:bff
area:docs
area:domain
area:event-subscriber
area:infra
area:portal-behandel
area:portal-beheer
area:portal-openbaar
area:portal-self-service
area:projection
area:workflow
type:adr-proposal
type:bug
type:chore
type:slice
No Label area:acl type:slice
Milestone
No items
No Milestone Iteration 1 — Walking Skeleton
Projects
Clear projects
No project
Assignees
Clear assignees
eho
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eho/register-referentie#46
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?