xray-junit-extensions (Not injecting changes to Test Issue Type) #45
Replies: 4 comments 2 replies
-
I think you're uploading the standard surefire JUnit reports and not the enhanced JUnit XML report generated by the listener on this project.
|
Beta Was this translation helpful? Give feedback.
-
It seems you're not using the report generated by this plugin; to to that you need to enable the listener EnhancedLegacyXmlReportGeneratingListener as mentioned here. Example: see this tutorial Note: You can always clone the tutorials at https://github.com/Xray-App/xray-junit-extensions and then adjust it to your needs. If you got it working, you'll have a new JUnit XML report where its contents will have those attributes like the test_key as |
Beta Was this translation helpful? Give feedback.
-
Hi, Finally got it working. :)
So i manually added the file(org.junit.platform.launcher.TestExecutionListener) in the location -> src/test/resources/META-INF/services/org.junit.platform.launcher.TestExecutionListener This generated the JUnit xml -> target/TEST-tests.CustomerDocumentTest.xml |
Beta Was this translation helpful? Give feedback.
-
Thank you so much :) |
Beta Was this translation helpful? Give feedback.
-
Hi,
I need help in how to exactly use xray-junit-extension.
The dependency I am using is
<dependency> <groupId>app.getxray</groupId> <artifactId>xray-junit-extensions</artifactId> <version>0.7.1</version> <scope>test</scope> </dependency>
Test Method:
@test
@DisplayName("Error Message")
@description("Validating error message")
@Xraytest(key = "TEST-336", summary = " Validating error message", description = " Validating error message")
@requirement("TEST-280")
@tags({@tag("Regression"), @tag("TEST-336")})
public void validateErrMessage(XrayTestReporter xrayReporter) throws InterruptedException, IOException {
xrayReporter.addComment("This test Validates error message for Foreign Country for Lithuania/Estonia/Latvia");
//Test Code
}
Jenkins:

Console o/p:

As you can see it is not updating the Issue Key - TEST-336 But creating a new Test Issue Key - TEST-344
Can someone please advice if the implementation is correct ? I am not sure what I am missing here.
Beta Was this translation helpful? Give feedback.
All reactions