N
Nikita_Nallamothu
Debuggability of test scripts during load testing is crucial for identifying and resolving issues early in the testing process. It allows you to validate the test configuration, understand the application behavior under load, and troubleshoot any issues that arise. Today, we are excited to introduce Debug mode in Azure Load Testing, which enables running low scale test runs with better debuggability and enhanced logging.
Debug mode is designed to help you validate your test configuration and application behavior by running a load test with a single engine for up to 10 minutes. It provides debug logs for the test script, and request and response data for every failed request during the test run. This mode is powerful for troubleshooting issues with your test plan configuration.
Here are some key benefits of using Debug mode:
Resource efficiency: Tests run in debug mode are executed with a single engine and are limited to a maximum duration of 10 minutes. This can help you identify the number of virtual users can be generated on one engine by monitoring engine health metrics.
Enabling debug mode is simple and straightforward. You can enable it for your first test run while creating a new test or when running an existing test. Just select the Debug mode in the Basics tab while creating or running your test and you’re good to go!
A screenshot that shows the option to run a test in debug mode.
Debug mode lets you see more information about your load tests, so you be confident that it runs as expected when run at high scale. It’s recommended to run the first test run in debug mode. Get started with Azure Load Testing here. If you already have been using the service, you can learn more about debug mode here. If you have any feedback, let us know through our feedback forum.
Happy load testing!
Continue reading...
Why Debug Mode?
Debug mode is designed to help you validate your test configuration and application behavior by running a load test with a single engine for up to 10 minutes. It provides debug logs for the test script, and request and response data for every failed request during the test run. This mode is powerful for troubleshooting issues with your test plan configuration.
Here are some key benefits of using Debug mode:
- Validation: Debug mode allows you to validate your test configuration and application behavior before running a full-scale load test. This can save time and resources by identifying issues early.
- Troubleshooting: With debug logs enabled, you can easily identify issues with your test script. This can be particularly useful when setting up complex test scenarios.
- Detailed error analysis: Debug mode includes request and response data for every failed request during the test run. This can help you pinpoint the root cause of any issues and make necessary changes to your test script or application.
Resource efficiency: Tests run in debug mode are executed with a single engine and are limited to a maximum duration of 10 minutes. This can help you identify the number of virtual users can be generated on one engine by monitoring engine health metrics.
How to Enable Debug Mode?
Enabling debug mode is simple and straightforward. You can enable it for your first test run while creating a new test or when running an existing test. Just select the Debug mode in the Basics tab while creating or running your test and you’re good to go!
A screenshot that shows the option to run a test in debug mode.Next steps
Debug mode lets you see more information about your load tests, so you be confident that it runs as expected when run at high scale. It’s recommended to run the first test run in debug mode. Get started with Azure Load Testing here. If you already have been using the service, you can learn more about debug mode here. If you have any feedback, let us know through our feedback forum.
Happy load testing!
Continue reading...