Right now, trying to map a test method to a Polarion TestCase and Requirement is tricky. This is because titles are not unique, only ID's are. For legacy reasons, we have autogenerated Polarion TestCases and Requirements, but there needs to be a way to decisively and uniquely map a test method from automation source code to its matching TestCase and Requirement.
Proposed Solution:
Java
Create a new Annotation class @PolarionTestCase that will reference the Polarion TestCase
Create a new Annotation class @PolarionRequirement that will reference the Polarion Requirement
Write a custom class that implements IReporter in TestNG to insert in the the matching annotations
Clojure
Include in the metadata for a test method, the above PolarionTestCase and PolarionRequirement
Ramifications:
This will require manually going through all the existing code and adding these annotations.
Also, pong should no longer autogenerate TestCases or Requirements. Sim's team is working on an exporter so that given an XML file, it will generate TestCases and Requirements.
Right now, trying to map a test method to a Polarion TestCase and Requirement is tricky. This is because titles are not unique, only ID's are. For legacy reasons, we have autogenerated Polarion TestCases and Requirements, but there needs to be a way to decisively and uniquely map a test method from automation source code to its matching TestCase and Requirement.
Proposed Solution: Java
Clojure
Ramifications: This will require manually going through all the existing code and adding these annotations.
Also, pong should no longer autogenerate TestCases or Requirements. Sim's team is working on an exporter so that given an XML file, it will generate TestCases and Requirements.