Even, if a compact version (current behaviour of latest version 1.6.1) is acceptable when you use third-party tool, it's impossible for a human to get a look on it !
console format is then the only one we can read easily.
My Goal : Provides a JUnit report either in a compact version or a human-readable format.
either to print a compact version (default behaviour) without --verbose option set
a human-readable version when --verbose option is set
My second goal is to propose also a checkstyle format that is more readable and reusable in third-party tool context.
FYI: I've begun to work on a project https://github.com/llaville/sarif-php-converters that propose to project like your to provide a SARIF report (when they have at least a checkstyle output format).
I've already a prototype for a CheckstyleFormatter class.
Hello,
Even, if a compact version (current behaviour of latest version 1.6.1) is acceptable when you use third-party tool, it's impossible for a human to get a look on it !
consoleformat is then the only one we can read easily.My Goal : Provides a JUnit report either in a compact version or a human-readable format.
I think it should be the original goal when we have a look on unit tests: https://github.com/shipmonk-rnd/composer-dependency-analyser/blob/1.6.1/tests/JunitFormatterTest.php#L79-L83 But in reality it's not TRUE !
I will propose a PR that fix this, and allow :
--verboseoption set--verboseoption is setMy second goal is to propose also a
checkstyleformat that is more readable and reusable in third-party tool context.FYI: I've begun to work on a project https://github.com/llaville/sarif-php-converters that propose to project like your to provide a SARIF report (when they have at least a
checkstyleoutput format).I've already a prototype for a
CheckstyleFormatterclass.Hope you'll like idea.