Integrate Azure Load Testing with CI/CD & JMeter-based Tests |

Explore the seamless integration of Azure Load Testing with CI/CD pipelines and JMeter-based tests, ensuring your applications can handle the increased traffic and deliver optimal performance during the busiest time of the year.
Discover how to leverage the combined power of Azure Load Testing and JMeter-based tests to identify and address performance bottlenecks early in the development lifecycle. Learn best practices for integrating load testing into your CI/CD workflows with Azure DevOps and GitHub Actions, enabling continuous performance monitoring and improvement.
Join us to enhance your performance testing strategies, streamline your development processes, and ensure your applications are holiday ready.
Skill Level - Intermediate
Further Learning: aka.ms/Quickst...
Speaker Bio: Nick Trogh
Nick is a technical writer at Microsoft, focusing on cloud testing and developer productivity services. Before this, he worked in developer relations, where he organized meetups, spoke at conferences, and helped developers do more with technology.
Off work, you can find him cooking, traveling, or exploring the Belgian lowlands on a mountain bike.
Social Handle: / nicktrogh
[eventID:20432]

[@Dannnn93]

Is there no way of retroactively creating these tests with a jmx file using your extension or have I missed something because the AzureLoadTest@1 documentation doesn't reference any ability to use a branched file for creation? Otherwise I'd have to resort to a CLI command to create a new test (not exactly difficult but would be handy).

[@Masudur-wd8ih]

If I have multiple jmeter scripts, do i have to create config.yml file for each test ? Can we include multiple test config.yml into one ?

[@Alamini96]

I have a quick question:
1. Is there a way of performing azure load tests where it doesn't bog down our production live app service ( besides creating a separate webapp for testing ? ).
Our use case is intermittent load testing so we don't want to create a service where 1 instance is always active and charged for even when load tests are not being run. Azure container apps is a way, but we're trying to see if something in azure load testing can let us do this without having to create new app services.