Skip to content
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

Added Sonarqube JUnit XML format #26

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

vignesh1001
Copy link

Hi,
We made some changes in index.js, sonarqube will not display all failures so we made some changes in xml preparation without effecting existing one.
Changed junit xml format preparation to the following way,

< testcase >
< error / >
< /testcase >
< testcase >
< failure />
< /testcase >
instead of
< testcase >
< failure />
< failure />
< error />
< /testcase >

Kindly update this changes, it may useful for sonarqube users.

Added new flag for old junit xml format
Changed JUnit xml preparation. Added new flag(sonarFormatFlg) to control xml preparation.if flag not mentioned or set as flase it will produce junit xsd.if it is set as true then it will format xml in sonar format  way.
@vignesh1001 vignesh1001 changed the title Added Sonar JUnit XML format change Added Sonarqube JUnit XML format change Sep 24, 2014
@vignesh1001 vignesh1001 changed the title Added Sonarqube JUnit XML format change Added Sonarqube JUnit XML format Sep 24, 2014
@vignesh1001
Copy link
Author

Hi @eventualbuddha ,
Could you please merge this changes and push it to npm.
Thanks,
Vignesh

@vignesh1001
Copy link
Author

This change is very useful for sonarqube user.so please merge this changes.it will not effect the existing flow.

Thanks,
Vignesh

@eventualbuddha
Copy link
Contributor

@vignesh1001 I have no write access to this repository and am not a maintainer of it. You'd be better off asking @vojtajina.

@vignesh1001
Copy link
Author

Hi @vojtajina ,
Could you please merge this commit and push it to npm.
Thanks,
Vignesh

@ReToCode
Copy link

Any updates on this?

@dignifiedquire
Copy link
Member

This needs rebasing onto latest master and cleanup to make CI pass first.

@ReToCode
Copy link

ReToCode commented Aug 15, 2016

Yep :) Is anyone going to do this soon? @vignesh1001 maybe?

@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.


  • If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
  • If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
  • In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants