API and log testing guides
Start with a task, inspect an actual result and repeat a check with downloadable sample data.
20 guides
API testing software without writing code
The example expects status to be OK. A second input changes it to ERROR and the same test fails. You can try this without connecting to a working API.
Open guide →Practical guideHow to create API tests without code
You will import a test case, run it against two inputs and see the exact field that differs.
Open guide →Practical guideAutomate API and log checks with Kibana
The request identifier selects the operation to inspect, and saved rules validate fields from the matching log data.
Open guide →Practical guideFind request logs by traceId in Kibana
You will know which value and field the search uses and can turn the selected log data into a repeatable check.
Open guide →Practical guideValidate required and unexpected JSON fields
The test checks required values and rejects an unexpected property. Its broken input demonstrates a real failure.
Open guide →Practical guideValidate every element of a JSON array
The downloadable example contains 1000 items. The broken input puts a defect at the end so you can verify that the test reaches it.
Open guide →Practical guideHTTP 200 but the result is wrong
The example changes a business status while keeping the test itself unchanged, showing why response fields need their own rules.
Open guide →Practical guideValidate JSON and XML API responses
You will separate data extraction from value checks and see how a deliberate mismatch appears in the report.
Open guide →Practical guideCreate API test drafts with local AI
You can review proposed test cases before adding them, then run the saved rules on passing and deliberately failing data.
Open guide →Practical guideImport cURL, OpenAPI and Postman requests
You can inspect an imported request, send it to a test environment and add explicit response checks.
Open guide →Practical guideChain API requests with extracted variables
The example extracts an identifier and compares it with a value in another part of the data. Use the same principle in a request sequence.
Open guide →Practical guideCreate a local API mock server
You can configure a local route, call it from an HTTP request and inspect the incoming request history.
Open guide →Practical guideRun API tests in Jenkins and CI pipelines
You will prepare a suite and identify its runtime, secrets and report settings before enabling unattended execution.
Open guide →Practical guideA Postman alternative for API and log checks
You can import a familiar request, add a field rule and inspect a log-based check before deciding whether Checkcraft fits your work.
Open guide →Practical guideCheckcraft security and data handling
You can separate the offline example, configured service connections and account operations before deciding how to use the application.
Open guide →Practical guideConfigure API request authentication
You will inspect the configured authentication and response status before adding business-result checks.
Open guide →Practical guideGenerate test drafts from documentation and screenshots
You will check the recognized material, review the proposed steps and prove the resulting test with a deliberate error.
Open guide →Practical guideCreate XML response tests without code
The example validates XML content and a tag whitelist. Its broken input makes a saved rule fail.
Open guide →Practical guideTest API totals, discounts and calculations
The example sums item amounts, stores the expected total in a variable and compares it with the returned total.
Open guide →Practical guideCreate conditional and negative API tests
The example checks an error code when status is ERROR and demonstrates a failure when that code is wrong.
Open guide →No matches. Try JSON, logs or AI, or .