You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at issues such as #62 and #69, it certainly seems like different users of this plugin have different needs concerning how the testcase attributes 'name' and 'classname' are generated. In our case, a recent change introduced in e4f7ebd is pretty much the exact opposite of what we need.
It should be easy to allow users to add functions to their configs to handle this – in other words, for the 'classname' attribute we'd allow overriding the 'getClassName' function, and add something similar for 'name'.
Would you accept a PR for this if I implement it?
The text was updated successfully, but these errors were encountered:
mleonh
changed the title
Allow name and classname generation overide
Allow name and classname generation override
Dec 9, 2015
I agree with @mleonh
We had a requirement to generate different classname but this was not possible with this reporter. Finally I had to process the xml report again to make it acceptable(for SonarQube).
mleonh
pushed a commit
to mleonh/karma-junit-reporter
that referenced
this issue
Dec 11, 2015
Looking at issues such as #62 and #69, it certainly seems like different users of this plugin have different needs concerning how the testcase attributes 'name' and 'classname' are generated. In our case, a recent change introduced in e4f7ebd is pretty much the exact opposite of what we need.
It should be easy to allow users to add functions to their configs to handle this – in other words, for the 'classname' attribute we'd allow overriding the 'getClassName' function, and add something similar for 'name'.
Would you accept a PR for this if I implement it?
The text was updated successfully, but these errors were encountered: