Skip to content

feat(core): rich scenario assertions — 8 assertion types + evaluateScenario() #100

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
sepehr-safari merged 1 commit into from
Jul 9, 2026
Merged

feat(core): rich scenario assertions — 8 assertion types + evaluateScenario() #100

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .changeset/v03-assertions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
---
'@ocpp-debugkit/toolkit': minor
---

Add rich scenario assertions — 8 declarative assertion types for scenario evaluation:
- `event_order`, `event_count`, `payload_field`, `timing`, `session_state`,
`failure_severity`, `no_failures`, `failure_count`

New API: `runAssertions()`, `evaluateScenario()`. Backward compatible —
existing scenarios with only `expectedFailures` work unchanged.
1 change: 1 addition & 0 deletions CURRENT_STATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,7 @@ integration examples, and contributor onboarding.
`SUSPICIOUS_SESSION_DURATION`, `SLOW_RESPONSE`, `HEARTBEAT_INTERVAL_VIOLATION`,
`METER_VALUE_ANOMALY`, `UNRESPONSIVE_CSMS` (15 total rules)
- ✅ Trace diffing — `diffTraces()` API (Issue #85)
- ✅ Rich scenario assertions — 8 assertion types, `evaluateScenario()` (Issue #86)

## What's Next

Expand Down
Loading
Loading