-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CxxXunitSensor in a multimodule project #612
Comments
I think some commit has been made later to fix some kind of corner case, The flag you mention I think it's to prevent every module to call all On Tue, Aug 18, 2015, 18:41 Peter van Zetten [email protected]
|
After removing I'll do a few more internal tests with a few other C/C++ projects, including a multi-module project using sonar-runner, and see if there's anything else that comes up. If it's clean I'll push for a PR. |
Ok, everything seemed fine after some additional tests, so I created PR #617. Please do check it out and try it locally though; I only tested in SQ 4.5.5 and with a few projects, so I'd be interested to see if it acts differently in any other configurations. |
Integration test for PR is failing. |
And it's failing on the multi module test, so you need it make sure that On Thu, Aug 27, 2015, 16:50 Günter Wirth [email protected] wrote:
|
Beside the fix for multi module project support the CxxXunitSensor should be improved to handle test results from multiple report files e.g. cppunit, gtest for a component as well.
|
please try again with 0.9.5:
|
We've realised (after not paying attention for a while) that we're not getting test execution reports for our C++ tests. It's not a vital feature of our SQ usage, but it used to work and I'm trying to narrow down why it doesn't now.
I'm not sure of the intent behind f2cedf7 and the general idea behind overriding
shouldExecuteOnProject
in the CxxXunitSensor. The commit message from @jmecosta introducing the override just states "prevent simple mode from running in all modules" and I can't figure out why that's desirable.As it stands, we can't get simple test execution reports in our multi-module project by any means. I haven't yet investigated getting detailed reports but this still seems like a regression. We're using a proper Maven project structure, so I guess a Sonar-Runner approach might treat modules differently and that's the source of the discrepancy. It would be nice to restore the simple reports for our use case.
Simply removing the overridden
shouldExecuteOnProject
method seems to result in the desired behaviour for our project, but I wouldn't submit a PR for this without fully understanding the original approach.The text was updated successfully, but these errors were encountered: