Content Check

This helps you to identify specific error message during executions and take appropriate actions as defined. Vugen uses content check to search for specific test strings automatically during executions using the pre-defined rules in the response returned from the server. You have in-built content check for applications like Siebel which will help to track down the error messages returned from the server and analyse the cause for script failure.

Lets see how this works:Consider you have defined a content check rule to search for Error “HTTP 404”, this might be due to bad request to the server or page might be missing or broken links. But server return “HTTP 404” simple. You have recorded a script which will access your banking application and navigate across different pages. When you run this script, what content check does is it will look through the responses sent from the server for the text string “HTTP 404”. When it finds this specific string content check stops the script executions or passes a warning message to the log file. This is just a simple example and overview on content check. In real time its really useful in different ways. You can fail script if particular text string is found as well for not found.

You can create your own content check for your applications by using the “new application button”, and then you can add individual rules as many to this. You can export content check you created by using the export option which is saved as .xml file. You can import the content check from other applications. Content check is stored as .xml file.