| 
|
| 
|
Data Format Extension requests
Some Web applications send or receive content which is unreadable by testers. Such applications are hard to load test because the content of the requests cannot be modified.
The Data Format Extension API is useful to read custom requests in the same way AMF, GWT, and other modules do. Natively NeoLoad converts the content of binary requests of a supported format into readable XML. When the existing modules (AMF, GWT, etc.) do not support custom formats, the Data Format Extension API helps testers have NeoLoad decode and encode requests. With the API used in a Java code, custom formats can be read. The API covers the HTTP and WebSocket transport layers.
Advanced Java programing skills are required to use the Data Format Extension API. See Data Format Extensions: Create an Encoder/Decoder.
Decoding a request or a response consists in the following operations:
- Receiving the request or response
- Detecting whether it can be decoded
- Converting the binary content into an object
- Converting the object into XML
- Storing the XML content in the request or response
Encoding is for requests only. It consists in the following operations:
- Generating the request with XML content
- Converting the XML content into an object
- Converting the object into binary content
- Storing the binary content in the request
The Data Format Extension API helps:
- identify whether a request or response can be decoded
- convert the binary content into an object
- convert the object into binary content
The other steps of the process are handled by NeoLoad.
Once the API is implemented in NeoLoad, it is invoked on recording the custom format application and to generate the load.
An API implementation must be exported as a JAR file before the file is specified in NeoLoad as described in Data Format Extensions.