Checkcraft in practice

Create XML response tests without code

Checkcraft is a desktop app for checking APIs and logs without code, with a free edition. Download, no sign-up →

An XML response may have the right outer shape while containing an incorrect value or an unexpected element. A useful test checks both the required content and the relevant structure.

Checkcraft team · Updated 10 October 2026

Get help with your first test →

How to repeat it Try Checkcraft

What you can verify

The example validates XML content and a tag whitelist. Its broken input makes a saved rule fail.

The XML contains ERROR instead of OK and an unexpected debug tag. The amount check passed. Actual detailed HTTP run report with rules next to the checked values. Open the screenshot to see the full run screen.

Choose the correct XML source

For XML inside a log entry, first locate the field that holds the XML. An XML tag check uses a tag path such as data/id. The ForEach XML step uses XPath to select repeated nodes. These are different inputs; follow the selected step’s help.

Check values and allowed tags separately

Add a value rule for a required tag, then use XML Whitelist for allowed child tags at the relevant node. A whitelist alone does not require every listed tag to exist. Add explicit rules for required content.

Exercise repeated nodes

When several item nodes are returned, use a loop and put the item checks after it. Place an invalid value in a later node to verify that the test inspects more than the first match. Keep the sample representative of namespaces and nesting used by your actual service.

Repeat the check with ready-made files

The quick experiment below runs in the test case editor. The screenshots show the detailed report available in HTTP run or Log run. For HTTP run, return the sample JSON or XML from a local mock and run the imported case against it, then open Results, Details and With structures. For Log run, load the sample into a log source, enable No request, run the case, then open Details and Detailed.

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 in English are available for the passing run and failing run. Sample names and literal data values do not change when you switch the interface language.

Inspect a SOAP response as XML

For SOAP over HTTP, agree the endpoint, SOAP version, content type and action first. Inspect the returned Envelope, Body and operation result or Fault. XML assertions can verify selected elements. HTTP success does not prove the absence of a SOAP Fault or full WSDL contract validation.

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 is available for Windows and Linux with no time limit.

Download Free Download and first run

No sign-up or email needed, the archive is ready in a couple of minutes. See the edition limits.