The following flow demonstrates how to get a list of Gherkin tests that are assigned to a developer and ready for automation.

In this topic:

Entity relationship diagram

We need to access the following entities for this flow, and understand the relationships between these entities.

Entity	Relationships in this flow	Description of relationship	Reference / relationship fields
Tests		This aggregate resource collection represents types of tests, including manual, Gherkin, test suites, and automated.	subtype
Gherkin Test	Test	The Gherkin test is a subtype of the tests aggregate resource collection. The Gherkin test can also be accessed in the gherkin_tests resource collection. There is no field that relates back to the aggregate resource collection, tests.
	Workspace user	A Gherkin test can be assigned an owner.	owner
	List Node	A Gherkin test has an automation status, such as Ready for Automation, Requires Update, or Automated.	automation_status

Back to top

Flows

Let's create the REST API calls step-by-step.

List my Gherkin tests that are ready to automate

1. We can start by listing all the Gherkin tests in the workspace.

   GET .../api/shared_spaces/<space_id>/workspaces/<workspace_id>/gherkin_tests

2. Let's build our query_clause. We are only interested in Gherkin tests that are assigned to me, and my ID is 1001.

   This query has two sets of criteria: The automation status, and the owner. We separate each set with a semi-colon (;), which represents the And operator.

   GET .../api/shared_spaces/<space_id>/workspaces/<workspace_id>/gherkin_tests?query="owner EQ {id EQ 1001}"

3. We also want to query the automation status to see which Gherkin tests are ready. This is an example of how to work with list nodes. One of the available lists in ALM Octane is automation_status, and we want to compare the Gherkin test's status with the automation_status list's value ready_for_automation. We use the logical_name field to check the list of automation statuses.

   GET .../api/shared_spaces/<space_id>/workspaces/<workspace_id>/gherkin_tests?query="owner EQ {id EQ 1001};automation_status EQ {logical_name EQ ^list_node.automation_status.ready_for_automation^}"

The complete REST API call for this part of the flow is: 

Back to top

Update the script of a Gherkin test

Assuming the first part of this flow returns one Gherkin test that is ready for automation, we now use that ID to update the script. In this flow, the ID of 1005.

PUT .../api/shared_spaces/<space_id>/workspaces/<workspace_id>/tests/1005/script

We PUT the following body, which contains the updated script. We make sure that the script conforms to Gherkin standards:

Back to top

See also:

• How to work with the REST API
• Common flows and ER diagrams