
Presenting Locust-Orchestrator For Executing Exhaustive Load-Plans
Hi Everyone... I am a DevOps & QA Engineer and I have been working on performance testing, as of late. While using Locust , I kept on thinking how nice it would have been if I could just perhaps input a CSV file with all things such as concurrent users, ramp-up and duration because in comparison and to this point, I had to key in all these individual items after each completion of the Load-Test. To combat this, I created a custom Locust Orchestrator to execute all of my test-plans in the background and let the reports get saved, for later reviews. Locust Orchestrator GitHub: https://github.com/dev-vaayen/locust-orchestrator It's a plain Python CLI, which allows us to specify a complete load test plan and run one after another with reports saved locally without any manual intervention in-between. What My Project Does: Performs several load tests based on a CSV file Prepares an HTML report on each test Logs when each test starts The plan.csv that is fed into the orchestrator works like t
Continue reading on Dev.to Python
Opens in a new tab
![[Learning notes and hw] getting started with R-cnn: Manually implementing Intersection over Union (IoU)](/_next/image?url=https%3A%2F%2Fmedia2.dev.to%2Fdynamic%2Fimage%2Fwidth%3D800%252Cheight%3D%252Cfit%3Dscale-down%252Cgravity%3Dauto%252Cformat%3Dauto%2Fhttps%253A%252F%252Fdev-to-uploads.s3.amazonaws.com%252Fuploads%252Farticles%252Favit2emoxc0g68e5ltqj.jpg&w=1200&q=75)



