Newman Version (can be found via newman -v):
3.9.4
OS details (type, version, and architecture):
macOS 10.13.5 64-bit
Node v10.4.1
Are you using Newman as a library, or via the CLI?
CLI (installed globally via npm -g command )
Did you encounter this recently, or has this bug always been there:
Not sure whether it was always been there.
Expected behaviour:
JUnit XML report generated should be compliant with JUnit.xsd
Command / script used to run Newman:
newman run ./API/MyProject.postman_collection.json --reporters html,junit,cli --reporter-junit-export ./NewmanOutput/90/Junit.xml --reporter-html-export ./NewmanOutput/90/index.html -e ./API/MyProject.postman_environment.json
Sample JUnit.xml generated :
<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="MyProject" time="4.779000000000001">
<testsuite name="GetCity" id="1f2b6fcf-0239-4dea-835f-136e355e269e" tests="1" failures="0" errors="0" time="0.482">
<testcase name="Status code is 200" time="0.482"/>
</testsuite>
</testsuites>
<testsuites name="MyProject" time="3.935">
<testsuites name="MyProject" time="4.779000000000001">
@Kiran-B Thanks for reporting this, a fix has been added in #1583 馃槃 The fix will be rolled out with the next Newman release.
@kunagpal, do you know when the next Newman release will be? I'm getting the same error and I'd rather not wait a few months until this is resolved.
@mgortzak @Kiran-B This has been fixed in Newman v3.10.0 馃槃
@kunagpal, I've ran 5 jobs, but still no error (or any other error for that matter). So it's fixed 馃憤 .
Most helpful comment
@mgortzak @Kiran-B This has been fixed in Newman v3.10.0 馃槃