Exploring the Coverage Map

The AIQ Blueprint Coverage Map shows you the multiple paths that the AI can take while interacting with the application being tested.

A Coverage Map allows you to visualize the health of the application being tested and understand all the potential user flows. You can easily see areas of the application that might be plagued by errors and require rework. Over time, the historical progression of the Coverage Map will also help you see where there is degrading performance, unexpected defect density, or other changes.

  • Click Coverage Map on the Blueprint Dashboard page to launch the coverage map for that Blueprint.

  • To open a Coverage Map for a Blueprint that is not currently running, navigate to Autonomous Testing > Coverage Map > Open Blueprint.

You should be aware of the following difference from previous AIQ releases. When logged in as the same user, you can no longer select the Coverage Map of another Blueprint while a different Blueprint is running.

For example, you have two Blueprints; Blueprint A and Blueprint B. Blueprint A is running and Blueprint B is not running. While Blueprint A is running, you can only access the Coverage Map for Blueprint A. You cannot access the Coverage Map for Blueprint while Blueprint A is running.

Interacting with the Coverage Map

You can to zoom in and zoom out to see more details including which actions and accessors are associated with a specific node. You can explore the Coverage Map in real time while the Blueprint is still running.

The colors of the various elements have the following meanings:

  • White: Not executed
  • Green: Executed with no errors
  • Yellow: Executed with an non-critical error, such as a 500 error.
  • Red: Executed with a critical error, such as a 404 error.
  • Blue: The execution path from the start point

  • You can select from the Coverage Maps for multiple executions (if you have them) in the Execution dropdown.

  • You can choose between three different visualizations of the Coverage Map. See Coverage Map Types for more information.

    The additional views of the Coverage Map were added in the 5.2.0 release of AIQ.

  • Click a specific node to see the actions and accessors. From here you will also see their exact location within the application being tested.

  • Click Generate DS Script to generate a script that contains the steps that the AI took to reach this specific page.

  • Click the Request tab in the detail window to see the associated requests.

  • You can search the URLs in the Coverage Map. Click on the results to see the page state details.

Filtering Requests

You can now filter out specific requests or errors (404 errors, etc) from the Coverage Map. This action will be saved to the Blueprint (.abpt) file so that the requests will not display when the Blueprint is executed in the future.

On the Requests tab you can see all requests for a node or the requests that have been hidden.

Hiding a Request

To hide a request, right click on it from the list and select Hide URL. The request is filtered out of the list and added to the Hidden Requests list.