Good First Issue
Add a new scenario meter-value-zero — a session where meter values are always zero (potential meter malfunction).
What to do
- Create
packages/toolkit/src/scenarios/__scenarios__/meter-value-zero.ts
- Create a synthetic trace with meter values all reporting "0" during an active transaction
- Set
expectedFailures: ['METER_VALUE_ANOMALY'] (zero is not negative, but is anomalous)
- Import and register in
packages/toolkit/src/scenarios/index.ts
- Update scenario count in tests
- Run
ocpp-debugkit ci to verify
Files to modify
packages/toolkit/src/scenarios/__scenarios__/meter-value-zero.ts (new)
packages/toolkit/src/scenarios/index.ts (register)
packages/toolkit/src/scenarios/index.test.ts (update count)
tests/external-fixture/test.mjs (update count)
How to claim
Comment "I'd like to work on this" and it will be assigned to you.
Please hold one open claim at a time. Once the pull request for it is merged,
say which issue you want next and it will be assigned. That keeps issues from
sitting claimed while another is still in review, so other newcomers can see
what is genuinely free.
Good First Issue
Add a new scenario
meter-value-zero— a session where meter values are always zero (potential meter malfunction).What to do
packages/toolkit/src/scenarios/__scenarios__/meter-value-zero.tsexpectedFailures: ['METER_VALUE_ANOMALY'](zero is not negative, but is anomalous)packages/toolkit/src/scenarios/index.tsocpp-debugkit cito verifyFiles to modify
packages/toolkit/src/scenarios/__scenarios__/meter-value-zero.ts(new)packages/toolkit/src/scenarios/index.ts(register)packages/toolkit/src/scenarios/index.test.ts(update count)tests/external-fixture/test.mjs(update count)How to claim
Comment "I'd like to work on this" and it will be assigned to you.
Please hold one open claim at a time. Once the pull request for it is merged,
say which issue you want next and it will be assigned. That keeps issues from
sitting claimed while another is still in review, so other newcomers can see
what is genuinely free.