karma-junit-reporter icon indicating copy to clipboard operation
karma-junit-reporter copied to clipboard

Published 20 hours ago • verified publisher icon karma-runner

Added Sonarqube JUnit XML format

Open vignesh1001 opened this issue 10 years ago • 8 comments

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.

vignesh1001 avatar Sep 24 '14 11:09 vignesh1001

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

vignesh1001 avatar Sep 30 '14 14:09 vignesh1001

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

Thanks, Vignesh

vignesh1001 avatar Sep 30 '14 14:09 vignesh1001

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

eventualbuddha avatar Sep 30 '14 15:09 eventualbuddha

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

vignesh1001 avatar Oct 01 '14 05:10 vignesh1001

Any updates on this?

ReToCode avatar Aug 15 '16 11:08 ReToCode

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

dignifiedquire avatar Aug 15 '16 11:08 dignifiedquire

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

ReToCode avatar Aug 15 '16 11:08 ReToCode

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).

:memo: 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.

googlebot avatar Jul 21 '17 04:07 googlebot