What to automate for a load test?

What are three main considerations to help determine what you should be automating for a load test, especially integrated load tests? To find out the answer, join my session today. I have three things that you can use to filter out unnecessary business processes and limit the scope of the testing to only what you need. Register at:

Thanks,

Scott

Page 1 / 1

As per me,

First, will be the identification of the modules which will be subject to load in routine use of application
Resources needed to run those tests are critical as you would want these automated load test should be running on developer’s machine as well
last one would be usefulness of those load tests, those should give actionable metrics.

1. Identify primary user journeys. This ensures your test simulates how real users interact with your integrated system under load.
2. Identify integration points and Evaluate resource utilization
3. Define achievable test scenarios and Monitor relevant metrics

1 Who are the users and what to they actually do on your system

2 Business risks and potential impact of bad performance a service

3 Cost

Reply

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded