notandClaude Opus 4.8
5180253826
BDD for S-10a: a registration parked at WachtOpDocumenten expires to VERLOPEN when the 30-day timer fires, and does NOT expire when documents arrive first. Drives the real RegistratieVerlopenProcessor + ExpireRegistrationWorker against an in-memory Flowable stand-in, mirroring the escalation feature. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
24 lines
1.3 KiB
Gherkin
24 lines
1.3 KiB
Gherkin
# language: en
|
|
# Drives S-10a (#102). After the zaak is opened the process parks at WachtOpDocumenten with an
|
|
# INTERRUPTING 30-day boundary timer. If the documents do not arrive in time the timer cancels the
|
|
# task and parks a RegistratieVerlopen job (ADR-0017) which the timeout worker drains, expiring the
|
|
# registration to VERLOPEN. Documents received before the timer fires close the wait, so no expiry
|
|
# happens. This scenario exercises the timeout worker against an in-memory Flowable stand-in; the timer
|
|
# firing live is verify-domain.
|
|
Feature: Een documenttermijn laten verlopen
|
|
Als registerbeheerder wil ik dat een aanvraag waarvoor de documenten niet binnen 30 dagen binnen zijn
|
|
automatisch vervalt zodat onvolledige aanvragen niet blijven liggen.
|
|
|
|
Scenario: Zonder documenten binnen 30 dagen vervalt de registratie
|
|
Given a registration parked at the WachtOpDocumenten task
|
|
When the 30-day document timer fires
|
|
And the document-timeout worker runs
|
|
Then the registration is verlopen
|
|
|
|
Scenario: Tijdig aangeleverde documenten laten de registratie niet vervallen
|
|
Given a registration parked at the WachtOpDocumenten task
|
|
When the documents arrive before the timer fires
|
|
And the 30-day document timer fires
|
|
And the document-timeout worker runs
|
|
Then the registration is not verlopen
|