Test with more than 15 users not You can carry out in these conditions, i.e. in a single machine, since it requires more than one machine testing the application. Making it on one machine, the maximum number of users allowed is 15, as the percent of CPU utilization must be less that 90%, if the test consumed more than that per cent, the results are false, and are not the real ones. Once defined the characteristics of the user group that you want to simulate (Test Plan > Thread Group) to see the load generated by the application, you create an HTTP Request Defaults (Thread Group > Config Element > HTTP Request Defaults), required parameters are specified as for example number ip server, port etc. A Proxy Server is then added (WorkBench > Non – Test Elements > http Proxy Server), where you specify where they will be stored samples. It gets to run the tool, and it begins to work in the application, step by step to obtain the report cases seen according to category of patients, to visit a page new application, samples taken from that page, added in a Transaction Controller (Insert Parent > Logic Controller > Transaction Controller). Once the navigation in the application, are added two reports one to see response times and another to be able to view errors found in this test (Thread Group > add > Listener > Summary Report and View Results Tree respectively). This report gives the response time of the application under the load of 15 users, is that the average response of the application time is 2 seconds, it takes me the minimum time is 0.047 second and the maximum time was 5.1 second.
The percent error was 50% which in analysis of the report reference is made to such errors. It also shows the performance of the application during the navigation was 14.9 seconds and a response from 134 KB/sec. With this report (View Results Tree) can get bugs found by each page visited, for example on the main page of the RAD, two were found errors (/general/style.css and /general/allstyles_aps.css) that according to the report says that it is not these files by requesting this page there is a delay, to make the request for those files that do not exist. 3 Conclusions there is a proposal for tools like JMeter for stress tests. In addition to a document more specific about the use of such a tool. With this tool you can analyze the performance of an application, under conditions specific i.e.
allows to analyze how it responds an application under the action of certain amount of users connected to it. 1Ramirez, Yilen Pons. 2007 Procedure for tests of efficiency under intensive load on web health applications. Havana: UCI, 2007. Original author and source of the article.