Web Transaction Tests

You can create a web transaction test in Traverse which can simulate a real user connecting to a web site, filling in a form, clicking on various hyperlinks, etc. This is a very powerful feature in Traverse which allows testing the response time and errors in most web-enabled applications.

The system is fairly intuitive with context-sensitive help and a mini-browser that displays the various stages of the web transaction. You can also save and even export/import this transaction for other sites.

Reusing the Same Web Transaction Test on Multiple Devices

Although you can specify any URL, the Web Transaction Test is intended primarily to test a web server hosted by the same device you created the test for. Typically the test is complex and unique to the web server you've chosen to test. Nevertheless, the same script can selected on the Advanced Test page of multiple devices. In this case, when creating the script, ensure the Replace URL hostname with the device address checkbox is checked, so that the starting URL specified by the script is replaced with the address of the device being tested.

Creating Web Transaction Tests

1. Click the Modify icon for any device, and then click Create New Custom Tests.
2. Scroll down to Web Transaction Test and click Manage Web Transaction Test Scripts.
3. Click Create Web Transaction Script.
4. Select No if you are not behind a proxy (typically the case).
5. Enter the URL you wish to monitor. This would be the same URL you would use when accessing the site in question using a browser. For tomcat monitoring, this would be: http://your_web_app_host /logon.jsp. If you wish to use the same script for multiple web servers, select the Replace this URL Hostname... option. Click Next.
6. The URL you have entered will be loaded and presented on a small window. This window is meant to show your progress on the web transaction. Do not click on any links on this window.
7. Various elements found on the page will be displayed to you on subsequent pages. You would select the element (for example, form, link) and an item from the selected element. For example, for the Traverse web application, if you wanted to log in you would select the form element logonForm and click Next.
8. Depending on what element/item you choose, you will be presented with corresponding options and as you progress through the transaction, the small Web window would show which page you are in. You can always consult this small window to determine which element/item you would want to pick from the transaction monitor.
9. When you have completed the session, it is time to close out the transaction script, so click Finished. The small window will be closed automatically.
10. Provide a unique name for the script and if you wanted to search for a specific text message during the session, you can enter it also.
11. Go back to device summary and click on modify icon for a device which has a web server running and is serving the content for which the script was created.
12. Click Create New Custom Tests and scroll down to Web Transaction Test.
13. Check the Provision box, provide a test name (For example, Traverse WebApp) and select the newly created script from drop-down list of Test Script.
14. Click Provision Tests.

    Note: You can create and manage transaction test scripts in Administration > Other > URL Transaction Test Scripts. Note that you cannot modify an existing transaction test.

    Note: The URL transaction monitor does not support JavaScript or similar browser scripting language. It is recommended that a separate page which does not have any scripting language should be setup for testing.