Hi,
I wanted to test the response xml of an application for both the
schema as well as the data. so I created a test plan as below
ThreadGroup
Simple controller
http request
XML schema assertion
view results tree
sample response of the application looks like as below
<?xml version="1.0" encoding="UTF-8"?>
<Search>
<contents>
<content name="nammakathappani">
<property language="eng" name="PPT" type="binary"
value="xxt_009114500003033_xxt.wav"/>
<property name="CODE" type="data" value="009114500003033"/>
</content>
<content name="bit">
<property language="eng" name="PPT" type="binary"
value="xxt_009110200006840_xxt.wav"/>
<property name="CODE" type="data" value="009110200006840"/>
</content>
and i have created corresponding xsd file for the above as below
<?xml version="1.0"?>
<!-- Generated using Flame-Ware Solutions XML-2-XSD v2.0 at
http://www.flame-ware.com/Products/XML-2-XSD/ -->
<xs:schema id="Search" xmlns=""
xmlns:xs="http://www.w3.org/2001/XMLSchema";
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
<xs:element name="Search" msdata:IsDataSet="true"
msdata:UseCurrentLocale="true">
<xs:complexType>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="contents">
<xs:complexType>
<xs:sequence>
<xs:element name="content" minOccurs="0" maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="property" minOccurs="0"
maxOccurs="unbounded">
<xs:complexType>
<xs:attribute name="language" type="xs:string" />
<xs:attribute name="name" type="xs:string" />
<xs:attribute name="type" type="xs:string" />
<xs:attribute name="value" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="name" type="xs:string" />
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:schema>
Now my problem is , i am getting error when response is compared with
this xsd file. I error is as shown below
fatal: line=14 col=6 The processing instruction target matching
"[xX][mM][lL]" is not allowed.
Please suggest me how to resolve this issue. I suspect this is occurring
due to the new lines involved just above to the actual xml content in the
response.
Or is there any other simple solution for easy testing of response xml
format...?
