Create Test
Tests
Create Test
POST
Create Test
Create a new test blueprint with a title, starting URL, and a sequence of steps.
Request body
Required fields
The name of the test. Must be between 1 and 128 characters and unique within your account.
The blueprint type. Must be one of:
"integration"— a standard end-to-end test"module"— an account/login module (requiresstarting_urlandcredentials)
To create reusable modules, use the Create Module endpoint instead.
An ordered list of steps for the test to execute. Required for
integration type.Optional fields
The URL the browser navigates to before executing steps. Must be a valid URL starting with
http:// or https://. Required when type is "module".A high-level description of what the test does. Used as additional context for the AI agent.
The ID of the test suite this test belongs to. You can find this ID in the Docket dashboard URL when on the Test Suites tab.
The folder path for organizing the test. Defaults to
"/".The device to run the test on. Must be one of:
"browser"— desktop browser (default)"android"— Android device"ios"— iOS device
The specific device name to use for mobile testing (when
device_type is "android" or "ios").The ID of the mobile app to associate with this test. Used for Android and iOS testing.
Browser zoom level. Must be between
0.75 and 2.0. Defaults to 1.0.Browser viewport width in pixels. Defaults to
1440.Browser viewport height in pixels. Defaults to
900.Number of automatic retries if the test fails. Must be between
0 and 3. Defaults to 0.Whether to reset the browser session on retry. Defaults to
true.Typing speed in milliseconds per character. Must be between
1 and 1000. Defaults to null (uses the default speed of 12ms).Whether to persist self-healed action caches so future runs use the healed selectors. Defaults to
true.How to handle file downloads during the test. Must be one of:
"save_only"— save downloaded files without processing (default)"ingest_content"— save and ingest file contents for the AI agent to use
Variables that can be referenced in step actions using
{{variable_key}} syntax.The ID of a module to run before the test steps begin. Useful for common setup tasks like authentication.
The ID of a module to run after the test steps complete. Useful for cleanup tasks.
The initial status of the test. Must be
"active" or "paused". Defaults to "active".Login credentials for
module (account) type blueprints. Required when type is "module".Example: Basic integration test
Example: Test with module, API step, and variables
Response
A confirmation message (e.g.
"Test blueprint created successfully").The created test blueprint object.

