Testing and QA
Tools for the part of testing that is not writing test cases: checking that a response matches its contract, and producing data adversarial enough to find out. Everything here runs in your browser and needs no account.
- API contract and response validation
- Test data generation, including hostile input
- Boundary values and equivalence partitions
- Reproducibility of test inputs across runs
Tools in this category
2 liveAPI Response Validator
Check a JSON response against a JSON Schema. Every problem comes back with its line, its path, and what to do about it.
- Duplicate keys. Legal JSON. Parsers keep the last and silently drop the rest
- Integers past 2^53. Rounded during parsing, before validation ever runs
- Branch reasons for oneOf and anyOf, not a bare "no match"
Test Data Generator
Realistic data with the values that actually break systems. Seeded, so the same configuration produces the same rows every time.
- Eight QA field types. Boundary integers and dates, right-to-left and zero-width strings, deliberate nulls and duplicates
- Reproducible for real. The generator version is recorded, not just the seed
- 100,000 rows without freezing the tab
Most testing tools assume your data is well formed
A validator that reports one error at a time. A generator that produces plausible names and valid emails but never an empty string, a right-to-left override, or an integer past what JavaScript can represent. Both are technically correct and practically incomplete, because whoever built them was not trying to break anything.
The tools here are built from the other direction. They report the failures that pass every other check: keys that appear twice and lose half the payload, identifiers that round before validation runs, values that are individually valid and wrong as a set.
Where these fit in a pipeline
Response validation belongs at the API or service boundary, with focused contract checks during pull requests and broader integration validation after deployment. Test data belongs wherever a suite has stopped being able to fail. If you cannot name a realistic change that would turn your contract tests red, they are not testing anything.