Executions

This chapter focuses on services for the executions.

Updates from version 1.2.0:

  • There are 3 types of execution: standard, scripted and keyword.

  • The "script" property is from now available only for scripted execution.

  • There is no longer "language" property in execution. The language for scripted execution is always GHERKIN while there is no defined language for standard and keyword executions.

Get execution

A GET to /executions/{id} returns the execution with the given id.

Path parameters

Snippet path-parameters not found for operation::RestExecutionControllerIT/get-execution-of-standard-test-case

HTTP request

Snippet http-request not found for operation::RestExecutionControllerIT/get-execution-of-standard-test-case

Request parameters

Snippet request-parameters not found for operation::RestExecutionControllerIT/get-execution-of-standard-test-case

HTTP response

Snippet http-response not found for operation::RestExecutionControllerIT/get-execution-of-standard-test-case

Response fields

Snippet response-fields not found for operation::RestExecutionControllerIT/get-execution-of-standard-test-case

Snippet links not found for operation::RestExecutionControllerIT/get-execution-of-standard-test-case

Create execution for iteration test plan item

A POST to /iteration-test-plan-items/{id}/executions creates a new execution for the iteration test plan item with the given id.

Path parameters

Snippet path-parameters not found for operation::RestIterationTestPlanItemControllerIT/create-execution

HTTP request

Snippet http-request not found for operation::RestIterationTestPlanItemControllerIT/create-execution

Request parameters

Snippet request-parameters not found for operation::RestIterationTestPlanItemControllerIT/create-execution

HTTP response

Snippet http-response not found for operation::RestIterationTestPlanItemControllerIT/create-execution

Response fields

Snippet response-fields not found for operation::RestIterationTestPlanItemControllerIT/create-execution

Snippet links not found for operation::RestIterationTestPlanItemControllerIT/create-execution

Modify an execution

A PATCH to /executions/{id} modifies the execution with the given id.

Path parameters

Snippet path-parameters not found for operation::RestExecutionPostControllerIT/patch-execution

HTTP request

Snippet http-request not found for operation::RestExecutionPostControllerIT/patch-execution

Request fields

Snippet request-fields not found for operation::RestExecutionPostControllerIT/patch-execution

Request parameters

Snippet request-parameters not found for operation::RestExecutionPostControllerIT/patch-execution

HTTP response

Snippet http-response not found for operation::RestExecutionPostControllerIT/patch-execution

Response fields

Snippet response-fields not found for operation::RestExecutionPostControllerIT/patch-execution

Snippet links not found for operation::RestExecutionPostControllerIT/patch-execution

Delete an execution

A DELETE to /executions/{id} delete one execution with the given id.

Path parameters

Snippet path-parameters not found for operation::RestExecutionControllerIT/delete-execution

HTTP request

Snippet http-request not found for operation::RestExecutionControllerIT/delete-execution

Get steps of execution

A GET to /executions/{id}/execution-steps returns all the execution steps of the execution with the given id.

Path parameters

Snippet path-parameters not found for operation::RestExecutionControllerIT/get-execution-execution-steps

HTTP request

Snippet http-request not found for operation::RestExecutionControllerIT/get-execution-execution-steps

Request parameters

Snippet request-parameters not found for operation::RestExecutionControllerIT/get-execution-execution-steps

HTTP response

Snippet http-response not found for operation::RestExecutionControllerIT/get-execution-execution-steps

Response fields

Snippet response-fields not found for operation::RestExecutionControllerIT/get-execution-execution-steps

Snippet links not found for operation::RestExecutionControllerIT/get-execution-execution-steps

Attach issue to an execution

A POST to /executions/{id}/issues attach an issue to an execution with given id. The identifier of the remote issue must be specified; however the bugtracker on which it is hosted is implied by the configuration of the Squash-TM project of the execution.

The actual format of the remote identifier depends on the type of bugtracker you are referencing. For example for issues hosted on Mantis the remote identifier is the ID, while for JIRA the remote identifier is the issue key. You can verify which format is expected in Squash-TM by testing first with the UI, eg in the table of known issues of an iteration.

Note that you cannot declare a new issue this way - post it straight to the bugtracker instead !

Path parameters

Snippet path-parameters not found for operation::RestIssueControllerIT/attache-issue-to-execution

HTTP request

Snippet http-request not found for operation::RestIssueControllerIT/attache-issue-to-execution

Request fields

Snippet request-fields not found for operation::RestIssueControllerIT/attache-issue-to-execution

HTTP response

Snippet http-response not found for operation::RestIssueControllerIT/attache-issue-to-execution