Load and performance testing is about simulating users, third-party systems, and batches and queries that interact with a system. Technically, with a tool like my prototype, you'll have everything you need to build test scripts, test definitions, and test objectives.įrom the moment you have all of your detailed http: traffic, you can fully automate the creation of performance tests based on situations you observe in production. Unfortunately, there is just too much missing information to automatically generate the load testing scripts. One of the biggest limitations is the lack of information stored in the http: logs or the data stored in APM products. Through this extraction, the program guides the project in building a continuous testing methodology for the client's main microservices. The objective was to present the 20% of calls that represent 80% of the production load. To help one of my clients build a realistic performance testing strategy, I built a program that extracts the use of its microservices in production.
That's why analyzing the traffic and application to generate your performance strategy is the most important task for creating your performance testing methodology. Generating load that does not reflect reality will only give you unrealistic feedback about the behavior of your system. How can you take advantage of application performance monitoring (APM) products and logs to define realistic load models for continuous testing?Ī realistic workload model is the core of a solid performance test.