Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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

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

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

Xray does not enforce any constraint on the "Generic Test Definition" field, as such this field so it is optional and you may use it as an additional field for quickly identify identifying what this test is all about.

...

The JUnit integration (see details in Taking advantage of JUnit XML reports) is a good example of how Generic Tests may be used as an abstraction of automated tests, independently regardless of the used testing framework and the technologies/platforms used. 


In general, you would follow this workflow.

Gliffy Diagram
namegeneric_tests_workflow
pagePin
 
1


  1. Create a Generic Test in JIRAJira.
    1. the 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 The test can be automaticaly automatically created in JIRA whenever 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 Jira (i.e., the issue key).
    1. this 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 In order to build the JSON file containing the test results, you will need to reference the Tests in JIRA Jira by their issue key.

 


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


Info
titleLearn more

See Automated Tests (Import/Export) for more info information on the Xray's JSON format and Import Execution Results - REST to know how to import those test results using the REST API.

 

 

 

 

...