Test using JUnit
Test Case Reusability
Link Requirements to Test Case
Introduction
JUnit is a simple framework for writing repeatable tests. It is an instance of the xUnit architecture for unit testing frameworks.
Automation Hierarchy | Test Cycle | Test Case | Test Step |
|---|---|---|---|
1 (Default) | NA | testsuite> name Or testcase > classname | testcase name |
2 | testsuite > name If there are multiple test suites in the result file then multiple test cycles will be created based on the suite name. If the testsuite name is not there in the file, it will take classname as test cycle name. → The parameter Test Cycle to Reuse will be ignored in the Automation. | testcase name | NA |
3 | The test cycle name will be created as per the Summary passed by the user. In the absence of the Summary, the test cycle name will be auto-generated. If there are multiple suites in the result file then only a single cycle will be created. → If the value is provided for the Test Cycle to Reuse parameter, then the suite name in the files will be ignored. All the test case results for all suites and files will be uplaoded in a single cycle similar to Hierarchy 1 (default). | testcase name | NA |
Note: If the Test Name or Test Suite Name length is more than 255 characters, the name will be truncated.
Supported Version: 1.2.5
Supported file types: XML
Sample Test Result File
The following is the screenshot of the file. Click
Users can auto-link stories with Junit test cases using the keyword "storykey" to specify the entity key in the result file. The specified stories will be linked to the created/reused test case.
Users can also link cross-project stories to the test case.
Users should have access to the cross project
Users should have the Test Case Edit and Requirement Edit permissions.
Multiple “storykey” can be used in the same tag in the file to link multiple stories to the test cases. e.g.
storykey="FIT-1 FIT-2 FIT-3 FTA-154"