This scenario takes you through the steps of documenting a transaction for a manual test.
You document the exceptions that occur in business transactions for a specific IP address using the recording feature.
Follow these steps:
The Document Transactions window opens.
The Record Case dialog opens. By default, the IP address displays for the system that is using the browser to connect to the DevTest Server.
You can change the IP address when you are running the browser that connects to the agent application from a remote system.
Including the test identifier from your ALM in the name is recommended. This name appears in the list of the Points of Interest portlet from the Home page.
The Start button changes to an animated Recording... icon to indicate that the recording is in progress.
The frames that are recorded display in the Captured Frames pane.
A purple pin is added to the frame of the IP address that is being recorded. The captured frames display automatically in the Captured Frames pane when Auto Refresh is selected. Otherwise, click the refresh button.
The recordings that are saved are listed in the Recording pane of the Document Transactions window.
You narrow the list of recordings to analyze using the search capability in the Document Transactions window.
Follow these steps:
The Recording pane of the Document Transactions window displays a list of all the recorded test transactions that were saved. You can view and analyze a recorded test in graphical or list view.
Follow these steps:
The test transaction opens in the lower pane in graphical view by default.
You can create a report of the transactions that were recorded during a test from the Document Transactions window. The report contains information about each frame that was recorded. You can save and print the report.
Follow these steps:
The report is generated and displays in a browser.
Note: It may take a few minutes to generate the report depending on the number of transactions.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|