It gets to run the tool, and begins to work on the application, step by step to get the report cases seen by category of patients, as they visit a new page in the application, samples obtained from that page, you add in a Transaction Controller (Insert Parent Transaction Controller Logic Controller). Once the browsing application, add two reports one to see the response times and another to see errors found in this test (add Listener Thread Group Summary Report and View Results Tree respectively). This report gives the response time of the application under the load of 15 users, we find that the average response time of the application is 2 seconds, the minimum time it takes is 0.047 seconds and the maximum was 5.1 seconds.
The percentage of error was 50% reporting that analysis refers to such errors. It also shows the application performance while browsing, which was 14.9 seconds and a response of 134 KB / sec. With this report (View Results Tree) can be found errors for each page accessed, for example in RAD’s homepage, there were two errors (/ general / style.css and / General / allstyles_aps.css) which the report says it will not find those files, when applying for this page there is a delay in making the request for these files, do not exist. 3 – Conclusions It has a proposed tools like JMeter for stress testing. In addition to a more specific document on the use of this tool.
With this tool you can analyze the performance of an application, under specified conditions is that it responds to analyze an application under the action of a number of users connected to it.