The Start Execution endpoint allows you to automate the execution of a model run.
POST request, you can enter parameter values to control the configuration of a model run, for example, which suite of snippets to run. You must specify the:
model_idfor an exploratory run, which is useful when you're building a model.
test_case_idfor a fully-configured model. If you start a run with only these two parameters, the model runs without connecting to any Eggplant Functional scripts and only generates a path through the model.
If you want to connect to an Eggplant Functional suite, you must use the agent to establish that connection, and give values for the parameters in the
POST -> http://localhost:8000/execution_service/api/v1/executions
You can also explore the Start Execution endpoint in Swagger:
To execute a model run, you must send a value for at least one of these parameters:
|For an execution run, the value is always
|UUID of the model to use for an exploratory or test case run.
|Agent that is used for the model run.
null then no agent is used.
|ID of the agent connection to use.
|Whether the agent is hosted or on the local machine.
|ID of the test case to execute for a test case run.
|Name of the script to use for a script-based run.
|Details of the test assets to use for test execution.
null then a model run without snippets is executed.
|ID of the asset version to use.
|Path of the suite to use on the connected agent.
|Details of the SUT to use.
|ID of the SUT.
|array of strings
|Criteria or tag of the SUT to lock. You can use this instead of the
|For a rerun, this is the test case ID of the original model run.
|For internal use only.
|Required parameters were not sent.
|The access token was not valid.
|Server denies access from the resource.
|Incorrect parameters were sent.
|RabbitMQ is not available
|Request cannot be completed because the message service is unavailable.
Response Body JSON
Successful response – Status 200 returns the ID of the model execution that has started.