In Test Workbench 9.1.1 we added several enhancements to Performance Tester. Check out the list and be sure to give them a try.
Viewing and sharing test results with our new reporting dashboard
Project stakeholders want to see test results without installing the workbench or being a workbench user. Now, in 9.1.1 with reporting dashboard, all the project stakeholders can view the test reports for functional and performance tests from a single web application. Stakeholders can access this dashboard from a web browser; so they donâ€™t need to install the workbench software. For those of you that use Performance Tester to test the performance aspect of the application, the dashboard the performance reports in an interactive fashion, with zoom and navigation as featured in the client software.
On the dashboard, itâ€™s easy to sort and filter test reports, get an entire view of your application from both a functional and performance perspective. For more detailed information about the reporting dashboard, be sure to read this blog post.
Recording a WebSocket test
What if you have an application using the WebSocket protocol and want to record and playback that technology? In 9.1.1 you can do just that. Keep in mind that WebSocket is not a separate test extension in the product. So, to test a WebSocket application, you record using theÂ HTTPÂ test type. After the recording completes, you donâ€™t want to delete or change the content of the requests, response, and connection objects in the test script. The requests and responses may contain text or binary data and you can do data correlation on the textual data. After the test run completes, you can examine the HTTP WebSocket Report, which gives you the number of requests attempted, succeeded, and the rate of success.
Assigning datapool values to multiple tests
In previous releases, to apply datapool values to multiple tests, you had to associate the datapool to each test. Now in 9.1.1, you can include a Datapool Mapper in a compound test or a test schedule to assign the datapool values to the variables that are defined in multiple tests. The Datapool Mapper maps the datapool columns with the variables.
Itâ€™s easy to use either the test editor to tell the Datapool Mapper to fetch the test variables or fetch the variables from custom code calls too. If you have tests or schedules that use different datapools, no problem. If the compound test or the schedule includes a Datapool Mapper that retrieves values from one datapool and a test in the compound test or schedule is also associated with another datapool, the run makes use of both the datapools.
When you run the schedule or compound test with a Datapool Mapper, by default the test picks up the datapool values from the first row. However, if you want the test to pick up all of the datapool values, just put the test in a loop action. Itâ€™s that easy.