Niek Otten
f02d2ef568
Gherkin scenarios for the two branches: a beoordeling left unclaimed for 14 days escalates to the teamlead, and one completed before the timer fires does not. Driven through the escalation worker against an in-memory Flowable stand-in. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
23 lines
1.3 KiB
Gherkin
23 lines
1.3 KiB
Gherkin
# language: en
|
|
# Drives S-14 (#15). A beoordeling a behandelaar does not pick up within 14 days escalates to the
|
|
# teamlead: a non-interrupting boundary timer parks a BeoordelingEscaleren job (ADR-0015) which the
|
|
# escalation worker drains, reassigning the still-open Beoordelen task's candidate group to teamlead.
|
|
# A beoordeling completed before the timer fires does not escalate. This scenario exercises the
|
|
# escalation worker against an in-memory Flowable stand-in; the timer firing live is verify-domain.
|
|
Feature: Een beoordeling escaleren
|
|
Als teamleider wil ik dat een beoordeling die na 14 dagen niet is opgepakt naar mij escaleert
|
|
zodat aanvragen niet blijven liggen.
|
|
|
|
Scenario: Na 14 dagen zonder oppakken escaleert de beoordeling naar de teamlead
|
|
Given a registration parked at the Beoordelen task for the behandelaar
|
|
When the 14-day escalation timer fires
|
|
And the escalation worker runs
|
|
Then the beoordeling is reassigned to the teamlead
|
|
|
|
Scenario: Een tijdig afgeronde beoordeling escaleert niet
|
|
Given a registration parked at the Beoordelen task for the behandelaar
|
|
When the behandelaar completes the beoordeling before the timer fires
|
|
And the 14-day escalation timer fires
|
|
And the escalation worker runs
|
|
Then the beoordeling stays with the behandelaar
|