not
ceb65991de
Completes the re-source (ADR-0030): the Event Subscriber's abonnement moves from `zaken` to `objecten`, in both the local stack's `nrc-subscribe` and the CI projection check. The OpenZaak → NRC check keeps its own `zaken` abonnement — OpenZaak still publishes, nothing in the product listens. - register-abonnement.py subscribes to `objecten`, and now treats the kanaal as part of "already current" — an abonnement left from before this slice points at the right callback but the wrong kanaal, and would never have been replaced on IP alone. - run-projection-check.sh opens its zaak *through the ACL* instead of straight against OpenZaak, because the ACL is what writes the register record the projection is now derived from. A zaak created behind the ACL's back produces no row — which is the re-source working. - The acceptance scenario is restated in register terms and gains the approval case: the same row moving INGEDIEND → INGESCHREVEN is now one registration's record being updated, not two unrelated ZGW events.
29 lines
2.1 KiB
Gherkin
29 lines
2.1 KiB
Gherkin
# language: en
|
|
# Drives S-19b-2 (#153), re-sourcing S-06 (#7). The read projection is derived from the
|
|
# RegisterRecord in Objecten (ADR-0030), not from ZGW zaak events: the ACL records a registration
|
|
# in the register, Objecten notifies, and the Event Subscriber projects the record that
|
|
# notification points at. This scenario exercises the use case against in-memory stand-ins for the
|
|
# register, the projection store and the notification log; real Objecten → NRC → subscriber
|
|
# delivery is verified by the live-stack check (verify-projection, ADR-0007/0030).
|
|
Feature: Register-projectie bijwerken op een registerwijziging
|
|
Als openbaar register wil ik dat een registratie in de projectie verschijnt zodra zij
|
|
in het register is vastgelegd, zodat het register haar actuele status kan tonen.
|
|
|
|
Scenario: Een ingediende registratie levert een rij met status INGEDIEND
|
|
Given registration "11111111-1111-1111-1111-111111111111" is recorded in the register with status "INGEDIEND"
|
|
When the register notification is delivered to the event subscriber
|
|
Then the register projection contains a row for "11111111-1111-1111-1111-111111111111" with status "INGEDIEND"
|
|
|
|
Scenario: Een goedgekeurde registratie werkt dezelfde rij bij
|
|
Given registration "33333333-3333-3333-3333-333333333333" is recorded in the register with status "INGEDIEND"
|
|
And the register notification is delivered to the event subscriber
|
|
When registration "33333333-3333-3333-3333-333333333333" is recorded in the register with status "INGESCHREVEN"
|
|
And the register notification is delivered to the event subscriber
|
|
Then the register projection contains a row for "33333333-3333-3333-3333-333333333333" with status "INGESCHREVEN"
|
|
|
|
Scenario: Dezelfde notificatie tweemaal levert geen duplicaat
|
|
Given registration "22222222-2222-2222-2222-222222222222" is recorded in the register with status "INGEDIEND"
|
|
When the register notification is delivered to the event subscriber
|
|
And the same register notification is delivered again
|
|
Then the register projection contains exactly one row for "22222222-2222-2222-2222-222222222222"
|