json-schema-org / json-schema-org/JSON-Schema-Test-Suite
beef up bignum tests
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 750
- Forks
- 307
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 24
Description
The "bignum" tests don't appear to be testing much. Most of them are missing boundary tests, and tests on either side of the boundary.
For example, the test for "exclusiveMinimum" should include a test above, below, and exactly equal to the argument.
Tests also be added for "enum" and "const" where applicable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating and reading the existing “bignum” tests in the JSON Schema Test Suite. Check each applicable boundary case, including exclusiveMinimum, enum, and const, and compare values below, equal to, and above the relevant boundary. Done means the tests cover those boundary conditions consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100