Page History

...

1. Implement the automated test code, store it in the source control system, and put the reference to the Test in Jira (i.e., the issue key).
   1. This depends on the testing framework: it can be as a "tag" or as the test name, if the framework supports that.
2. Execute tests in the CI environment.
3. Report execution results using the format specific to the automation framewoek (either using the REST API directly or through Bamboo/Jenkins add-ons).
4. Create our update existing Tests in Xray
   
   1. In the first iteration, Tests will be automaticaly created in Xray and the Generic Test Definition field will act as the test identifier (e.g. classname plus classmethod corresponding to automated test). Xray is able to identify uniquely from the report file
   2. In second and onward iterations, existing Tests will be updated; Xray will use the Generic Test Definition field as the test identifier in order to find the existing Test in JIRA
   3. Depending on the test automation framework being used, links can also be automaticaly created between the Tests and the requirements

After Tests are created in Jira, they can be managed in Jira. Thus, users can add additional information to them, associate them with other entities (e.g. requirements, Test Sets, etc)..

Manual provisioning

You may also create yourself Generic Tests as an abstraction of some test, so you can track its results in Jira. Generic Tests are great if you don't need to have a structured Test composed of steps (otherwise you would have to use Manual Tests as abstractions).

...