Clean-room nomination · Tests and edge cases

Tests and edge-cases test: repair and test integer ranges

This test measures two abilities together: implementing a strict input contract and writing meaningful tests that catch plausible incorrect implementations, not merely the seeded defect.

Nomination prepared · results pending
Public testsvisible parsing checks
Objective evaluatorunseen behavior + mutations
4 criteriaseparate blind review
2 allowed filessource and authored tests

Test assignment

Make integer-range parsing strict and prove it with tests

The model receives a faulty parseRange(value) implementation and a public test file. It must repair the parser and extend the tests with cases strong enough to reject realistic broken variants.

What the implementation and tests must cover

  • Accept only a string containing exactly start..end, with optional whitespace around the complete value.
  • Require both sides to use signed base-10 integer syntax: an optional + or - followed by digits.
  • Reject decimals, exponent notation, hexadecimal syntax, missing sides, extra separators, and non-string values.
  • Accept only values from -100000 through 100000, inclusive.
  • Reject reversed ranges where the start is greater than the end.
  • Add focused tests for boundaries and invalid formats; the objective evaluator also mutation-tests the authored suite.
Allowed files: fixtures/phase2-v2/tests-edge-cases/src/range.js and test/range.test.mjs

How each reviewed solution will be scored

Each criterion receives 0–10. Public behavior, the objective evaluator, and mutation-test evidence remain separate from the manual score.

Functional correctness

How completely the parser implements the documented integer-range contract.

Reliability / edge cases

How thoroughly the code and authored tests cover syntax, boundaries, reversed ranges, and invalid types.

Maintainability / clarity

How readable and focused both the parser and its test cases are.

Scope discipline

How strictly the solution stays in the two allowed files without weakening or bypassing evaluation.

Overall is the arithmetic mean of the four scores.

Results are not published yet

This page defines the test before model execution. The future table will show public and objective results, mutation-test evidence, four review scores, time, cost, and runtime route.

Public contract

Inspect the fixture and public tests ↗