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

test(acl): BDD acceptance scenario for opening a zaak (closes #5) #49

Merged
eho merged 3 commits from test/5-acl-bdd-acceptance into main 2026-06-08 11:25:28 +00:00
Conversation 0 Commits 3 Files Changed 9
+206
3 Commits
Author SHA1 Message Date
ehoandClaude Opus 4.8 e9e6269dc8 docs(architecture): ADR-0004 — Reqnroll as BDD framework (refs #5)
CI / lint (pull_request) Has been cancelled
Details
CI / build (pull_request) Has been cancelled
Details
CI / unit (pull_request) Has been cancelled
Details
CI / compose-smoke (pull_request) Has been cancelled
Details 
Record the choice of Reqnroll.xUnit for the acceptance layer introduced in
S-04, and register the previously-unlisted ADR-0002/0003 in the MkDocs nav.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 11:17:22 +02:00
ehoandClaude Opus 4.8 389d35fd39 feat(acl): wire BDD step bindings to AclService (refs #5) 
Implement the step definitions for EenZaakOpenen.feature against the
existing AclService, with an in-memory gateway standing in for the OpenZaak
Zaken API. The scenario now passes: a domain registration is default-filled
into a ZaakRequest (ADR-0003) and the created zaak URL is returned.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 11:16:38 +02:00
ehoandClaude Opus 4.8 1fba877de9 test(acl): BDD acceptance scenario for opening a zaak (refs #5) 
Introduce a Reqnroll.xUnit acceptance project under tests/acceptance/ and
the first Gherkin scenario driving S-04: the ACL default-fills the
ZGW-mandatory zaak fields (ADR-0003) from a domain registration payload.

Red: the scenario is discovered but has no step bindings yet, so it fails
with undefined steps. The green commit wires the bindings to AclService.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
 2026-06-04 11:14:11 +02:00