Annotation shows wrong class path on multi-module project
Closed this issue · 2 comments
I work on a large multi-module Maven project. In some cases, a given class and method name are used in more than one module.
We've begun using this action for our JUnit 4 test reporting quite effectively, but recently ran across a case where the annotation for a unit test failure reported the wrong class path:
The first line of annotation reported that the error occurred in the azure module, but if you download the logs or even just click on the "Raw output" button in the annotation you can see the error was actually in the mq module.
Each of these modules does have a WorkProviderTest.messageToTask method. The log and raw output correctly report which one had the failure, but the first line of the annotation gets it wrong.
With #61 the annotation should be shown in the correct file now when package names are different.
Feel free to reopen if you still face the issue.