Managing automated Tests

Whether your tests are manual or automated, in the end you will need to have visibility of the results of all your tests, independently of how they are executed.

Your test results will affect the status of your requirements in the same way, no matter if they're manual or automated.

As a team member, you will need to evaluate your requirement coverage at any moment. For this, you need to link your Tests with your requirements, and report your automated test results from your CI environment.

Xray for JIRA is the ideal tool for managing automated Tests, because you manage manual and automated tests essentialy in the same way.

 

The standard way for managing Tests would start by creating them in JIRA and proceed from there. This logic can be applied also to automated Tests.

 

However, with automated tests and Agile teams, normally tests are written during development and in a continuous way. Keen developers will add as many tests as possible, or at least the most relevant ones.

Thus, the most common workflow when dealing with automated tests would be to write the automated tests, and their specific code, execute them and then import the results and the test themselves to Xray.

Note that in the final step, Tests are only created as entities in JIRA only if they are "new" Tests. This means that the Tests must be uniquely identified.

 

Type of Tests used for automation

Xray provides two different type of tests that may be used to represent automated tests:

• Cucumber: a test specified in natural language (i.e. in Gherkin)
• Generic: all other automated tests (or any automated test in general)

 

 

Understanding responsibilities

It's important to understand how the different tools fit together and what are the main responsibilities of each one.