Generate Endpoint Test Cases
Use Generate tests on the endpoint test-case screen to create critical tests first, then fill coverage gaps—across many test strategies with business-impact severity.
Help Center
Browse articles in this category, or use search to jump to a specific task.
13 articles.
Use Generate tests on the endpoint test-case screen to create critical tests first, then fill coverage gaps—across many test strategies with business-impact severity.
Edit a test's request, assertions, and expected response; run and delete in bulk; and use the coverage verdict to find the gaps your suite still has.
Define environments, variables, headers, and datasets so tests run consistently across dev/stage/prod without hardcoding secrets or setup.
Choose where tests run: Shift-Left Engine on server for CI/CD and schedules, or Shift-Left Agent locally for development and private APIs.
Run endpoint test cases from the actions column, monitor progress, and review detailed test-result summaries with assertions and logs.
Control per project which requirement types the AI extracts, which test strategies fire, and which severity tiers are kept—so generation focuses on what matters for that project.
When a test fails, use Fix with AI to get a proposed patch you can review and apply—plus a fix-suggestion lifecycle that classifies whether the failure is a bad test or a product bug.
Many APIs don't take JSON. A login or OAuth token endpoint may expect an HTML-style form. An avatar or document upload expects a multipart form with a file in it.
Read assertion results row by row (expected, actual, passed), and write custom checks whose script log appears right under the result when they fail.
How Fix with AI grounds each proposed repair in your API contract, your requirements and the last run, and what the workbench Diagnostics show about what was actually sent.
Shift-Left Studio tests JSON-RPC 2.0 services and Model Context Protocol (MCP) servers alongside your REST, SOAP and GraphQL APIs. An MCP server is a JSON-RPC 2.0 server with a fixed set of methods, so the same capability covers both.
Some services are not called with independent HTTP requests. You open a WebSocket connection, sign in once during the handshake, and then send a series of calls over that same connection.
Test endpoints that answer with text/event-stream: see each event in the response viewer, assert on events, and stream with limits on events, duration and idle time.