xray-automated-tests-ids

name	xray-automated-tests-ids
description	Obtains the IDs of automated tests from JUnit XML reports, similar to the ones used by Xray on generic tests.

Test automation IDs used by Xray

This skill is designed to obtain the IDs of automated tests from JUnit XML reports, similar to the ones used by Xray on generic tests. It analyzes the JUnit XML files generated by test executions, extracts the relevant information about each test case, and produces a list of test cases with their names, type, corresponding ID, and statuses.

Possible flows for obtaining test automation IDs

There are 3 possible flows to obtain the test automation IDs, depending on the context and the information available:

1. If the JUnit XML files are available, the skill can directly analyze them to extract the test case information and produce the list of test cases with their IDs and statuses.

2. If the JUnit XML files are not available, but the project is a Maven or Gradle project, the skill can first run the tests to generate the JUnit XML reports, and then analyze them to extract the test case information and produce the list of test cases with their IDs and statuses.

3. If the user doesn't want to run the tests or if the project is not a Maven or Gradle project, the skill can analyze the test code to identify the test cases, their types. In this case, it will ignore the statuses.

Type of tests

Tests can be of different types, such as unit tests, integration tests, functional tests, etc. The type of test can be determined based on the naming conventions used in the test classes and methods, as well as the structure of the JUnit XML reports. For example, unit tests may be identified by the presence of "Unit" in the class name, while integration tests may have "IT" in their names. However, the specific conventions may vary depending on the project and the testing framework used.

Output example

When asked to provide the IDs of automated tests from JUnit XML reports, the output should be a list of test cases with their names, type, corresponding ID, and statuses, formatted in a clear and concise manner. For example:

findAllReturnsAllUsers,unit,com.sergiofreire.xray.tutorials.springboot.UserRepositoryTest.findAllReturnsAllUsers,PASSED
getDefaultGreeting,integration,com.sergiofreire.xray.tutorials.springboot.GreetingControllerMockedIT.getDefaultGreeting,FAILED