Google Web Toolkit requests

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.

Note: 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.

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. For more information, 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.

Post-recording wizard

When the recording is finished, and if there are Java classes missing, the JAR declaration panel is displayed:

  • You need to load the Java classes for the objects being exchanged, as well as the client interfaces for the called services.

  • This panel only displays part of the missing classes; not all the missing classes can be resolved.

To declare the missing GWT Java libraries (JAR and GWT.RPC files), follow these steps:

  1. Open the file explorer by clicking the + button.

  2. Select an appropriate WAR file for the application, or the directory containing the deployed web application, then click Select. NeoLoad automatically retrieves the required JAR and GWT.RPC files from the selected application. You also may select the JAR and GWT.RPC files to be loaded manually in NeoLoad. Repeat the operation as many times as is necessary.

  3. A message confirms the declaration. If the operation fails, make sure that all the required GWT Java libraries have been declared.

If the declaration has been a success, the following screen appears:

Declaring the GWT Java libraries at the end of recording is a compulsory step if all the requests are to be played back.

  • You may declare missing GWT Java libraries at a later stage.

  • Declaring GWT libraries is carried out in the project's GWT libraries manager in the project preferences. For more information, see Google Web Toolkit.

GWT requests with missing GWT Java libraries are identified by a warning symbol: