Load Testing Blog Article 4, occurs if the errors are not a problem. You will then look at the evident indicator, of the applications response time. It means the time required, for your application to respond to a user action. You also have to consider the three phases prior to Part #4 phase:
Part #1- Correlations,
Part #2- Data Driven Testing, and Assertions
Part #3- Top 4 Timer.
Advanced Load Testing Blog 4, as the final blog post- when the stepping thread group, are convenient and stable. By adding the user steps, it let us know:
* Increased thread load by portions
* Decrease load by portions
* Configure hold target load line
* Determine the parameters as standard thread group
You can analyze the Load Testing Article 4 by taking the following 7 steps:
Check response times, if you search a document by a keyword, so you will receive request from SQL server.
Load testing tools and measure any client-side parameters
Make sure WAPT provides the local time with page elements, and value of the report- Response time, sec (page element)
Check the line required to execute successive request, by joining the request
with the help of the Task Operator. The operator is used to join the page
request and you have two options:
Measure full task from beginning to end
Calculate task time of execute request and delay between them
Download time is measured from the first byte received to the last byte by:
If the response time for HTTP is different, you may get another value. The best approach is, to collect the average response time.
The average value should be= Ave 90=9.
To analyze the performance of your web application, you will need to consider the average values and time intervals. The WAPT will provide the number of request, for each test phase, and you will be able to see “Response Time”, for Loading Testing Blog 4.