Checkcraft in practice

How to create API tests without code

If the same response needs checking after every release, save the expected result once. A useful first automated check is small enough that you can explain why it passes and why it fails.

Checkcraft team · Updated 14 September 2026

How to repeat it Example files

What you can verify

You will import a test case, run it against two inputs and see the exact field that differs.

Actual Checkcraft interface. This reference screenshot was recorded in Russian. Full size ↗

Create a place for the check

Create a workspace, then use the tree context menu to create a collection, a check and a test case. In the test case editor, use Import to load the file below. Import adds a new test case instead of replacing the one you have open.

Make the expectation explicit

The example checks status against OK. This is an expected business value, not an inference that every HTTP 200 response is correct. For your own API, take the expected value from the contract or an agreed requirement.

Prove the check can fail

Paste the valid JSON with Paste data for analysis and click Run test case. Then paste the broken JSON and run the same steps again. Open Result and read the failed rule. Keep this negative example when you change the test.

Repeat the check with ready-made files

Download the Checkcraft test case and two inputs. One input is valid, and the other contains a deliberate error. These synthetic examples are available without registration.

Importable test case JSON Valid data JSON Broken data JSON

Run the example in Checkcraft

Create a collection, a check and a test case using the workspace tree context menu. Click Import in the test case editor and choose the downloaded test case. Open the added case, copy the valid JSON, click Paste data for analysis, then Run test case. Open Result to inspect the report.

Repeat with the broken JSON without changing the rules. The first run should pass and the second should fail. If you see a different outcome, check the selected data source, imported steps and report.

The example files were executed against the application source on 14 September 2026. Reference reports recorded in Russian are available for the passing run and failing run. Sample names and literal data values do not change when you switch the interface language.

Try your own check

See the result on a small example first

Start with the sample, inspect the failure and then try a sanitized example from your own API. Free (beta) is available for Windows and Linux with no time limit.

Get Free (beta)Download and first run

An account and verified email are required to obtain the build. See the edition limits.