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

ADR proposal · Adopt Reqnroll as the BDD acceptance framework #48

New Issue
Closed
opened 2026-06-04 09:19:51 +00:00 by eho · 0 comments
eho commented 2026-06-04 09:19:51 +00:00
Owner
Copy Link

Per CLAUDE.md §14, adding a dependency / choosing the acceptance-test framework warrants an ADR. S-04 (#5) is the first slice with behaviour to drive via Gherkin (§3, §11), so it introduces the BDD tool.

Proposal: Adopt Reqnroll.xUnit (maintained SpecFlow successor) for tests/acceptance/, generating one xUnit test per scenario so acceptance tests run under the same dotnet test / make ci gate.

Decision recorded in: docs/architecture/adr-0004-bdd-framework.md (lands in the PR that closes #5). This issue exists to track the decision per process; it is closed by that PR.

Per CLAUDE.md §14, adding a dependency / choosing the acceptance-test framework warrants an ADR. S-04 (#5) is the first slice with behaviour to drive via Gherkin (§3, §11), so it introduces the BDD tool. **Proposal:** Adopt Reqnroll.xUnit (maintained SpecFlow successor) for tests/acceptance/, generating one xUnit test per scenario so acceptance tests run under the same dotnet test / make ci gate. **Decision recorded in:** docs/architecture/adr-0004-bdd-framework.md (lands in the PR that closes #5). This issue exists to track the decision per process; it is closed by that PR.
eho added this to the Iteration 1 — Walking Skeleton milestone 2026-06-04 09:19:51 +00:00
eho added the type:adr-proposalarea:docs labels 2026-06-04 09:19:51 +00:00
eho closed this issue 2026-06-08 11:25:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:acl
area:bff
area:docs
area:domain
area:event-subscriber
area:infra
area:portal-behandel
area:portal-beheer
area:portal-openbaar
area:portal-self-service
area:projection
area:workflow
type:adr-proposal
type:bug
type:chore
type:slice
No Label area:docs type:adr-proposal
Milestone
No items
No Milestone Iteration 1 — Walking Skeleton
Projects
Clear projects
No project
Assignees
Clear assignees
eho
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eho/register-referentie#48
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?