Skip to content

No test for parseVerdict with mixed-case verdicts in same text — case-insensitive last-wins untested #375

Description

@devinoldenburg

Problem

tests/verdicts.test.mjs has a case-insensitive test for single verdicts, but no test like:

"VERDICT: pass\nVERDICT: FAIL"

to verify case-insensitive last-wins behavior.

Suggested Fix

Add:

test("parseVerdict uses last match case-insensitively", () => {
  const result = parseVerdict("VERDICT: pass\nSome text\nVERDICT: FAIL");
  assert.equal(result.verdict, "FAIL");
});

Expected behavior

The affected workflow should behave consistently with the project intent described in the title: No test for parseVerdict with mixed-case verdicts in same text — case-insensitive last-wins untested should either be handled correctly, documented clearly, or covered by regression tests so users and maintainers can rely on it.

Actual behavior

The current implementation, documentation, or test coverage does not address this case as described above. The issue body captures the observed gap and the file/component where it was found.

Impact

Leaving this unresolved can cause confusing user behavior, missed regressions, weaker safety guarantees, or maintenance friction depending on the affected component. It is worth tracking separately because the finding is specific and actionable.

Duplicate check

Before/while filing, open issues were reviewed and searched by the main keywords from this title. No exact open duplicate was intentionally kept; if maintainers identify overlap later, this issue can be consolidated into the older/more complete report.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesttestingTest infrastructure

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions