Page History

...

In this scenario, common if you're using JUnit, TestNG, NUnit, xUnit, Robot framework, developers/testers write the automated tests as code accordingly with the automation framework being used.

After that, they just need to submit the results to Xray and it will automaticaly automatically create Test entities for each of them (or update existing ones if they already exist), so you have visibility of the automation results in Xray. 

...

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 framework (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 automatically created in Xray and the Generic Test Definition field will act as the test identifier (e.g. classname class name plus classmethod class method 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 automatically created between the Tests and the requirements

...

...

1. Create a Generic Test in Jira.
   1. The test will be uniquely identified by the issue key; however, the Generic Test Definition custom field may be used as a more friendly way to identify the test (e.g., with the name of the test class/method, name of the script or executable implementing the test).
   2. The test can be automatically created in Jira when importing test results; as mentioned in the previous point, the Generic Test Definition field acts as the test identifier.
2. 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.
3. Execute tests in the CI environment.
4. Report execution results using Xray JSON format (and optionally, the REST API).
   1. In order to build the JSON file containing the test results, you will need to reference the Tests in Jira by their issue key.

...

...

...

You can use Generic Tests as means to abstract some exploratory session. You can use the Generic Test Definition field to identify the session charter (e.g. goals of that session/mission).

During the execution of your session, you can attach evidence, report if all went fine and if not you may create defects. You may also decide to create a Manual Test, with the reproducible steps, for validating that the problem does not arise in the future.