Google Web Toolkit requests

In This Section Overview Post-recording wizard User Interface

See Also Requests HTTP requests SOAP requests WebSocket requests Oracle Forms requests Adobe Flex/AMF requests Adobe RTMP requests Data Format Extension requests Hessian requests Java serialization requests Siebel requests Silverlight requests Media requests Polling requests Streaming requests Push messages Validation Global validation Variable extractors Advanced parameters Variable correlation Shortcuts Compare requests and responses

Overview

GWT (Google Web Toolkit) is the AJAX Framework developed by Google. It allows asynchronous remote procedure calls to be executed between the client and server, using GWT-RPC (Remote Procedure Call) procedure: the resulting data exchange is binary, encapsulated within the HTTP protocol.

The GWT module makes it possible to load test applications programmed with the GWT framework and using the GWT-RPC protocol.

To be able to handle GWT requests, it is necessary to purchase the optional Google Web Toolkit module. This module is included in the demo version of NeoLoad.

For more information, click the image below to see the Neotys video about GWT in NeoLoad:

Dependent libraries

When recording GWT-type requests, you need to load the Java classes for the objects being exchanged, as well as the client interfaces for the called services. See Google Web Toolkit.

Recording

The following diagram shows how the Google Web Toolkit module works during the recording:

The binary data exchanged between the client and server pass through the recording proxy. The Google Web Toolkit module comes into play as the data travels through the proxy, analyzing and decoding the requests. Once translated into XML, the requests are inserted in the project.

Execution

The following diagram shows how the Google Web Toolkit module works during a test run:

The XML request variables are evaluated and the module engine translates the XML to binary data. This data is then sent to the server. The binary response received is translated into XML and the validations and Variable Extractors of the played request are executed.

Home