The Parasoft Event Details perspective is designed to help you view and explore test events. You can open this perspective in any of the following ways:
- Click the Parasoft Event Details button in the shortcut bar (on the top right of the workbench).
- Click the Open Perspective button in the shortcut bar, choose Other, then choose Parasoft Event Details in the Open Perspective dialog that opens.
- Choose Window> Perspective> Open Perspective> Other, then choose Parasoft Event Details in the Open Perspective dialog that opens.
Viewing Events
The monitored events will be displayed in the Event Log view. They will be presented in the order in which they occur, then structured to represent test logic (loops, scenarios vs. individually-runnable tests, etc.).
Events reported include:
- Test start and end
- Request messages received
- Response messages sent
- Data source row usage
- Errors
- Wait times
- Navigation
For example, here is what event details might look like for an API test scenario where the tests run as a group (SOAtest runs all tests for each row of the data source):
For another example, here is what event details might look for a set of individually-runnable API tests (SOAtest iterates through all data source rows for each test).
For a final example, here is what event details might look like for a web test scenario:
Note that if you are also using Parasoft Virtualize for service virtualization—and you are testing against virtual assets on a Virtualize Server with monitoring enabled—the Event Details perspective will report both SOAtest test events and Virtualize server events.
Exploring Events
You can explore events as follows:
To achieve this... | Do this... |
---|---|
Focus on the events related to a specific test suite or test | Select the related node in the Events Explorer view |
See more details about an event | Select the related event in the Event Log view |
Clear the current information and start a new session | Click the Start New Log button |
Review one of the 5 most recent logs | Choose the appropriate log from the Event Log’s History drop-down menu |