![]() ![]() The advantage of this functionality is that existing scripts from QF-Test can be integrated easily into a load test and the load test with the metric of the End User Experience contains new possibilities of evaluation.įor load tests few substantial business processes are needed that then are replayed in a high number to reach a realistic system load. The performance tester can change the degree of detail of the values’ recording via the configuration himself. The graphic shows that the values can vary widely. The upper graph shows the duration of the advanced action and the lower of the selected test case node on the left. In the right part of the screenshot there are two graphs. In the left part of the screenshot on the image above you can see the structure of the test script in QF-Test shown as folders. ![]() test case nodes or sequences) is delivered from QF-Test to the NeoLoad controller. The integration makes it possible that both software products test cases can be called up in QF-Test by specialized advanced actions in NeoLoad. The graph is only uncertain, because the time to access the test execution software is added as well, which is not clear for the evaluation. Via the test execution report the performance tester can access different performance measurements e.g. The integration saves time for manual capturing of NeoLoad scripts as the transfered NeoLoad script structure is comparable.ĭifferent symbols of the different QF-Test actions help to gasp the user path optically. It is possible to migrate already existing testcases developed within QF-Test efficiently and partly automated in NeoLoad. The difference between response time and End User Experience shows how much time was spent for content processing and rendering by the browser. This integration adds the measurement of End User Experience to existing load test scenarios. On their basis we developed an integration that gives answers to the two above mentioned questions. The test automation tool QF-Test from Quality First Software and the load test tool NeoLoad offer interfaces. An integration between these two tool types can reduce the effort a lot. ![]() Test automation tools and load test tools have different concepts, so this reuse has certain limitations. If in addition to already existing automated tests load tests should get executed too, it is certainly advanteagous if these scripts can get reused. Usually test automation tools test the functionality of an application in projects that already use test automation. This metric is often called End User Experience and can be measured with this integration. In consequence the question when the end user is able to see a reaction in the browser arises. ![]() This visualization may be time consuming withinin today’s web applications, because most often HTML-structures are created via scripts on the client dynamically. However when the response arrives on the client’s side, additional operations may be needed before this information can be visualized, e.g. When load tests are executed with a load test tool, usually the response time is defined by the duration of sending a request and receiving the response. In projects where test automation and load testing is playing a role, two questions frequently arise. Muth Partners GmbH, Wiesbaden, Germany – November 2017 Motivation for the integration ![]()
0 Comments
Leave a Reply. |