Automating Load and Performance Testing Before releasing any new application into production, it is essential to carry out extensive Load / Performance testing. The purpose of Load/ Performance testing is to identify and resolve all the performance bottlenecks before the system goes live and to ensure that the end users are not affected by performance related issues. Infrastructure constraints such as CPU and memory limitations can be identified, resolved and retested to ensure the most cost-effective configuration. The Performance Test execution can be automated when there is a need to run it much more frequently. In reality, manually setting up and running a single automated performance test doesn’t take that long, running several test over a short period of time calls for automation to trigger performance tests. Automating the execution of Load / Performance test can be easily performed by integrating the load test into Continuous Integration (CI) tools like Jenkins or Circle CI. Any of those tools can trigger an external process. The performance testing challenges are far beyond test execution. Performance testing is tricky and time consuming. Many aspects still require human intervention, including test design, test script maintenance, identifying bottlenecks and analysis of test results. Performance test results could go grossly wrong, if the workload is not simulated properly. In order to get more accurate performance test results, it should be tested on a workload model which is very similar to the production environment. A good understanding of the application and its usage pattern are vital for carrying out the work load modelling. Workload modelling is the core activity in the performance testing. A workload model will provide the various parameters (types of application users, key business scenarios, their relative distribution, target load levels etc.) required to simulate in the performance test. The data necessary to create the workload model is typically not directly available. The performance test collaborates with the application stakeholders, network team, business and marketing teams for obtaining the required information. The approach to performance test workload modelling will be discussed in detail in this presentation.