I'm running a scenario from the command prompt (via batch file) in NoGUI mode. The test launches fine, but when finished, gives the error above in the command prompt and neoload.log file. I've attached the log file from the time period in question, along with the batch file I'm using to launch the project. This has worked with other HTTP projects, but now I'm using it for Web Services testing and we're getting this strange error message.
Could you try to open that file "C:\Temp\Smoke_PPR_WS_JUnitResults.xml" related to the Junit report? Is the content valid?
Also could you try to save that file elsewhere instead of the Temp folder?
The process may not have rights to write files at the root of the C:\ folder. You should try another folder and make sure anyone can write into it.
Also please confirm that the content of the Junit file is correct when it gets created.
I'm confused. Looking at the output from the test execution the reports have been successully created without any error. And you do not have anymore the parsing error that you mentioned in the beginning of that thread.
The exit code is due to the SLA thresholds that you set in your project. When they fails the exit code is 1 and 0 if they succeed.
If you would like to override that exit code you can use the "-exitCodeFailIgnore" option in the command line.
The test failed in the exact same manner as before, I just didn't copy the neoload_log file to my last response. I need the JUnit xml file to be created so I can verify if the SLAs are being met. I'm automating this process and integrating with UCD/ALM, so I'm relying on a Java process to parse the JUnit XML file and establish whether or not SLAs are met. This SAXParseException is prohibiting the JUnit XML file from being created, which will cause my automated process to fail. Attached is an excerpt from the neoload log file that captured the error from this morning. Nothing has changed since I first raised this issue.
I tried to reproduce your issue with different settings but on my side it always worked. You said that on your side it also worked for other HTTP projects so i guess the issue is specific to your project.
I also used Web Service requests in my project and NeoLoad 6.3.1 to stick as much as possible to your setup with the same parameters but never succeeded to reproduce.
Could you tell me if "B_Inquiry_Medical" is a user path name or else?
I think that the issue might be due to an unescaped characters in the name of one of your user path, transaction or request. Could you check if you do have any special characters in any names?
