Using PureLoad and PureTest for both manual and automated tests does lead to significant savings in test-time.
Using the PureLoad Runner by which you can automate your performance tests.
The first step to automate a load test is to create the actual test scenario (test case). This is done by using the Console (graphical user interface). Once your test scenarios are working, save them on file. Then you can execute your tests using the provided Runner command line interface or use the Runner Java API to integrate with a test framework.
The PureLoad Runner is available with PureLoad Enterprise as well as PureLoad Enterprise Developers Edition. Read more about the automation support in our documentation.
Having the automation support available also for PureLoad Enterprise Developers Edition gives you a low cost option to build assurance against basic performance degradation already during early test activities like build tests.
With automation possible both for PureTest and PureLoad it is now possible to close the DevOps bridge in a smart and cost effective manner.
Test cases that have been developed for execution in a function test environment (PureTest) or in a performance test environment (PureLoad) can easily be automated. The same test cases can also be run in the Operations environment during live operation.
When using the same test cases in all environments you simply change load servers and monitor points in the operations environment . In this way you get data so you can compare results from the development environment with results from the live operations environment.
Using the PureLoad KPI functionality will significantly reduce the cost for deployment of CI and test automation implementations. A significant portion of the CI Jobs contains KPI measurment and control and is today manually implemented using test scripts.
With PureLoad KPI functionality you can:
PureLoad also has a Jenkins plugin available to show KPI results.
