Niek Otten
ddebfd371a
BDD scenarios (Gherkin/Reqnroll) driving S-12's decide flow: a behandelaar takes an INGEDIEND registration into behandeling and decides it goedkeuren (→ INGESCHREVEN, zaak status via the ACL) or afwijzen (→ AFGEWEZEN, no ACL). Feature-scoped bindings avoid clashing with the identically-phrased status step in RegistratieIndienen. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
25 lines
1.2 KiB
Gherkin
25 lines
1.2 KiB
Gherkin
# language: en
|
|
# Drives S-12 (#13). A behandelaar picks up a submitted registration for beoordeling and decides it:
|
|
# goedkeuren enters it in the register (INGESCHREVEN, the zaak's final status set via the ACL, §8.1),
|
|
# afwijzen turns it down (AFGEWEZEN). This scenario exercises the use cases against in-memory
|
|
# stand-ins for the ACL and the store; real Flowable user-task claim/complete arrives in a later
|
|
# sub-slice and is verified live.
|
|
Feature: Een registratie beoordelen
|
|
Als behandelaar wil ik een ingediende registratie beoordelen
|
|
zodat deze wordt ingeschreven of afgewezen.
|
|
|
|
Scenario: Goedkeuren schrijft de registratie in via de ACL
|
|
Given a submitted registration with an opened zaak
|
|
When the behandelaar takes it into behandeling
|
|
Then the registration has status "INBEHANDELING"
|
|
When the behandelaar decides "goedkeuren"
|
|
Then the registration has status "INGESCHREVEN"
|
|
And the zaak's final status is set via the ACL
|
|
|
|
Scenario: Afwijzen wijst de registratie af zonder de ACL
|
|
Given a submitted registration with an opened zaak
|
|
When the behandelaar takes it into behandeling
|
|
And the behandelaar decides "afwijzen"
|
|
Then the registration has status "AFGEWEZEN"
|
|
And the ACL is not asked to set the zaak status
|