Page History

Generic Tests may be used in several ways: as exploratory or non-organized manual tests; they can also be used to have visibility of your automated tests in Jira.

A "Generic" Test can be used as an abstraction of an automated Test, so that it can be managed in Jira, linked to requirements, and we can report on its related results.

Basically, you manage Generic Tests the same way as you would do for other Test Types.

A Generic Test It is uniquely identified by the issue key. We , but you can also use the Generic Test Definition field to somehow identify the Test (e.g., by setting it with class and method that implements the test code, or the automated script file name).

...

Not yet available but will be added in future versions with the to support of JUnit, TestNG and other formats.

Manual provisioning

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

These Tests can be implemented as code in our own custom framework and you may report results back to them by using the REST API and Xray's JSON format.

...

In general, you would follow this workflow.:

...

If you have a project already being validated by automated tests which are not in Jira, you may create the Generic Tests in bulk either by building a CSV and import it or by using Jira's REST API (see example here). 

...