CheckcraftData-driven API testing with CSV and Excel exports
Get help with your first test →
A request needs repeating with several inputs. Manual copies make it harder to track which input failed.
This workflow needs an active Pro license and a build containing Pro scenarios. See the edition details.
Prepare the source request
Create a Pro scenario using a saved check and request. The example assumes {{customer}} is used in the relevant request field and the test service returns HTTP 200 with status CREATED. Adjust these illustrative expectations for your own contract.
id,name,var.customer,expect.status,expect./status
normal,Normal order,alice,200,CREATED
second,Second customer,bob,200,CREATEDPreview the dataset
Paste CSV in the scenarios and data tab and preview the parsed rows. Keep a unique, stable id when editing a row. var.customer defines a variable, expect.status the HTTP status and expect./status the JSON field value. These are distinct expectations.
Use an Excel worksheet
Create the same columns in Excel and export CSV. This does not claim native binary XLSX import. Verify UTF-8, comma delimiters and quoting around values containing commas. Spreadsheet regional settings may produce another delimiter.
Run and retry failures
Save the scenario, choose an environment and run the dataset. After fixing the cause, retry failed rows from the last run of that scenario. Check prior side effects before repeating writes. Functional dataset execution is not load generation.
Start with the linked example and compare its result with your own test requirement.