Running automation in Playwright, Cypress, Selenium, or your CI/CD pipeline but results are scattered everywhere? The Auto Create a Run API is designed to solve exactly that—send automated test results directly to PractiTest without manually creating tests, instances, and runs in advance.
What This Endpoint Does
When you send a request to Auto Create a Run, PractiTest automatically:
- Looks for the relevant test (or creates it if it doesn’t exist)
- Looks for an instance in your specified Test Set (or creates it)
- Creates the automated run result
One API request. Full automation. Your results end up in PractiTest alongside your manual tests—unified dashboards, traceability, and reporting.
Two Mapping Approaches
Option 1: Map by Test ID
- Use this when tests already exist in PractiTest
- You have full control over which test receives the result
- Best when your team manages test cases in PractiTest and wants explicit mapping
Option 2: Map by Test Name
- Use this when starting a new automation integration
- PractiTest finds the test by name or creates it automatically
- Best for teams that want faster setup without manual mapping
- Keep test names stable and unique to avoid creating duplicates
How It Works
Most automation integrations follow the same pattern:
- Run your automated tests
- Capture the result
- Convert the framework result into a PractiTest payload
- Send the payload to the Auto Create a Run endpoint
Integration Points by Framework:
| Framework | Common Integration Point |
|---|---|
| Playwright | Custom reporter (onTestEnd) |
| Cypress | Node event (after:spec) |
| Selenium | Test framework hook (after test) |
| Postman/Newman | JSON reporter output |
| Robot Framework | Listener or parsed output XML |
| CI/CD tools (Jenkins, GitHub Actions, GitLab CI) | Post-test reporting step |
What You Can Report
Basic (Test-Level):
- Exit code (0 = Passed, anything else = Failed)
- Run duration
- Execution output (short summary, up to 255 characters)
Advanced:
- Step-by-step execution with individual step statuses
- File attachments (screenshots, logs, HTML reports, trace files—up to 50 MB)
- Custom fields
- Test attributes (name, description, test type)
Start simple with test-level reporting, then expand to steps and attachments as needed.
Why This Matters
Unified Testing Picture: Manual and automated results in one place. One dashboard. One source of truth for release readiness.
Less Manual Work: No more manually creating tests or instances in PractiTest. No mapping spreadsheets. Automation flows in automatically.
Better Traceability: Link automated runs to requirements, track coverage, and prove what you’ve tested.
Compliance & Visibility: Stakeholders see the complete testing story—not scattered reports across multiple tools.
Full Integration Guide: 
Auto Create a Run API Documentation
Now we’d love to hear from you:
Are you currently integrating automation results into PractiTest? How are you doing it—Auto Create a Run, manual mapping, or something else?
And what’s your main goal with the integration—unified reporting, requirement traceability, release visibility, or something different?
Share your approach in the comments below! 