Schema compliance assertion export
Hi, I would like to not just export the schema compliance assertion by exporting the testcase log, but would like to export it to an excel file for each test request in my test loop... I'm not too...
Forum Discussion
Hi Robert, you're right, I was running the steps individually so I could monitor the output directly.
Running the testcase in its entirity, the preceding teststep is found by the script so thx for that...
I do however get some unwanted results from the script though.
When I run a testcase where I know a schema compliance issue will be raised, the result from the script is for example: "[Lcom.eviware.soapui.model.testsuite.AssertionError;@c8010f", which is not quite the same as the more specific "org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA" I get in the standard assertion.
It might well be ofcourse that c8010f is an error code for this particular schema compliance deviation but is there some way this can be verified or is there another way to get the more specific message?
Strangely enough though, even when a reply conforms to the schema and therefore passes the schema compliance without error raised, I still get a similar message with the script ([Lcom.eviware.soapui.model.testsuite.AssertionError;@630657) as opposed to the built-in assertion that just lights up green...
Running the testcase in its entirity, the preceding teststep is found by the script so thx for that...
I do however get some unwanted results from the script though.
When I run a testcase where I know a schema compliance issue will be raised, the result from the script is for example: "[Lcom.eviware.soapui.model.testsuite.AssertionError;@c8010f", which is not quite the same as the more specific "org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA" I get in the standard assertion.
It might well be ofcourse that c8010f is an error code for this particular schema compliance deviation but is there some way this can be verified or is there another way to get the more specific message?
Strangely enough though, even when a reply conforms to the schema and therefore passes the schema compliance without error raised, I still get a similar message with the script ([Lcom.eviware.soapui.model.testsuite.AssertionError;@630657) as opposed to the built-in assertion that just lights up green...