Hey everyone!
As a QA engineer, I know how hard it is to create real, data-driven performance tests. Managing dynamic test data and finding the actual breaking point of an application can be a real headache.
Recently, I built a complete test environment to solve this problem. I wrote a 3-part series about my solution, and the final architectural deep-dive is now published on ITNEXT.
In this article, I explain:
• Setting up a local target app with Docker and simulating 1,000 concurrent users.
• How to dynamically use CSV files in JMeter for data-driven testing.
• How to run heavy tests without GUI mode (CLI mode) to save system resources and get accurate results.
(Note: You can also find the links to Part 1 and Part 2 inside this article if you want to see the basics!)
If you want to improve your performance testing skills, I think this will help you. I also shared my code snippets and configs.
📖 You can read the full story here:
https://itnext.io/jmeter-performance-testing-part-3-finding-the-breaking-point-with-data-driven-scenarios-0d7b7924b5a3
I would love to hear your feedback! How do you handle massive test data in your own projects?
Top comments (0)