Hello, I am using this tool WAPT3.0 for performance tests of a web-application, and so far I ran 5 test scenarios with different number of users and iterations for each user but I don't understand the results - i.e. diagrams and logs, maybe I must understand more the server side of the product? And I can't figure out what am I testing - the server abilities and capacity or the performance of my application running on it...
thank you in advance, any advices will be OK
The results shows the number of requests made to the server and the time taken for response and number of concurrent users made etc...
you right click on the test and click on properties to see the settings made for the users and counters.
Hope this helps.
I have one more query..when i start recording using ACT the browser settings are defaulted to 8181 port and when i change the settings in browser to 8080 it is not recording.
Originally posted by sudir_ks: I have one more query..when i start recording using ACT the browser settings are defaulted to 8181 port and when i change the settings in browser to 8080 it is not recording.
<font size="2" face="Verdana, Arial, Helvetica">ACT recorder is a proxy that listening to the port 8181 so when you change settings in browser ACT recorder still listening to the port 8181 and records nothing.
The things that ACT/ANY PERFORMANCE TEST TOOL does when testing for performance of an application are giving the results of the variables that are considered to be major / become major bottle necks in the application for the response times so it would be better before you plan the performance testing of the application try yourself issolating the variables. for e.g.
1. response times of the application.
2. queries that are taking more time.
3. network bandwidth.
4. various other constraints according to which the delay in the times of the requests are set. apart from these we can also use code and SQL profilers to look into the part of the code that is taking more amount of time.
the above things that i have mentioned are only a small part of variables there would be lot of variables considering the type of the application and the business logic requirement.
it would be good to have proper and methodical plan to test rather than just testing for test sake. testing should be a full time one in parallel with development to fine tune the application.