Testing

Description

Testing section

Testing Section will facilitate the functional test of some components of GreenVulcano^® ESB.

In this area the user can populate the fields of the input objects (as example a GVBuffer instance) and display the service's execution result. The input object fields, such as the output, changes depending on the requested test.

GV Console Configuration

Testing is a Web application that provides a GreenVulcano^® ESB service invocation facility, simulating a client request.

In this area you can test the already configured services.

The configurable tests in Testing Area are related to the following sub-systems:

• Core to test the direct call to the EJB of GreenVulcano’s Core.

The Testing view is divided into three sections:

• Data input
• Test output
• Exceptions

Data input

GV Console Testing data

For a test that accepts a GVBuffer input object the display appears as shown in the following figure:

GVBuffer input Object has default values already set, as Id, but can be changed by the user, or been generated using the "getId" function. In the case of insertion by the user, we recall the normal rules for compiling the ID (unless you want to test the case of incorrect ID insertion):

• Length of 24 hex digits.
• Must contain only upper case letters from A to F.
• Not end with 0000.

If user enters incorrect values, the application will however attempt to execute the test and returns an exception.

All the text box for entering input GVBuffer values are editable.

These fields are part of the test environment:

Test output: file writing

• Output File Name: name of the file where the last test output will be saved;
• Input File Name: name of the file where the last test input will be saved;

Iteration number

• Iterator Number: number of invocations to be run using the same payload;

In case of iteration of the same test, the GVBuffer input will be the same but the Id is regenerated for each test. It is also possible to define a file that contains all the looped test output.

These fields are specific for test that accept a GVBuffer input:

• ID: transaction unique identifier;
• Service: name of the Service to be invoked;
• System: name of the Client System to be simulated;
• ReturnCode: numeric return code;
• Character Encoding: payload encoding;
• Payload: input data to be sent;
• Properties: input GVBuffer properties;

Management of properties requires the inclusion of multiple name-value pairs with the button Properties.
Moreover, each inserted pair can always be eliminated by clicking on [del] icon.

• Transaction Mode: transaction management;

• Forward Name: name of the forward to be invoked.

Upload Data

Regarding the Payload, the user has the option to insert the value in the text box or upload a file with the value by the UPLOAD function.

In case of using the UPLOAD function, the Text Area will contain the selected file content.

The UPLOAD function allows the selection of a file and the file content encoding:

• Binary
• US-ASCII
• ISO-8859-1
• UTF-8
• UTF-16BE
• UTF-16LE
• UTF-16

If user wants to upload a binary file, the text box of the Payload field will be replaced by a showData button that just displays the binary data in the form of hex dump.

To reset the Payload field to a text box just click the resetData key.

The choice of encoding will change the display of the Payload field. This view, to be correct, requires that you save the file in the right encoding, where it is required by the UPLOAD function.

For executing the tests, the page offers a number of buttons as there are GreenVulcano^® ESB standard workflow names to test.

Parameters for the connection to EJB Given the specific features of the test to invoke the EJBs, you can set the connection parameters through the "Set JNDI Parameters" link. This Link proposes a series of useful parameters for an invocation of an EJB and then: JNDI Name: Name of the EJB to be invoked (Required) JNDI Factory: FQN of the application server specific context factory Url: Connection factory URL User: Application server User Password: Application server Password The text box will always be editable and propose in the first instance the default values specified in the configuration file: GVSupport.xml This file will be configured through the GreenVulcano® ESB interface. If the user change these parameters, the values will remain so for the duration of the test and are resetted to the configured ones.

Test output

Single Test Output

Both for single test than iterated test, the application does not eliminate the input, but still maintains the view to facilitate the comparison with the output data.

Based on the service expected output format, the application will give the possibility to choose between Show Binary, which presents the binary data in a hexadecimal dump, and Show as text, which presents the data as a string (with encoding to be chosen in a combo box).

Five iteration output

In case of iterated test run, the output is presented as the following figure:

The ID is generated at run time and will be different for each iteration. By the link "Output" you can see the result of single test, specifying the encoding type.

Exceptions

Wrong Paradigm Error

If the service returns an exception it' visualized with the stack trace. The following picture shows a service invocation failed because the user invoke the wrong Operation: