DevOps is a practice that unifies people, process and technology across development and IT in five core practices: planning and tracking, development, build and test, delivery and monitoring and operations. When practicing DevOps, development, IT operations, quality engineering and security teams work closely together—breaking down practices that were once siloed.
Apache Jmeter is most widely used open source tool for load testing .Now we can run jmeter tests on Azure DevOps. This blog will illustrate that how to run the tests.
Before you start your load testing:
- Create your Azure DevOps subscription, if you don’t have one already.(You can use free trial subscription as well. so you can create by using gmail account)
To run a JMeter load test:
1. Sign into Azure DevOps account.
2. Click “+Create Project” to create a project .
3. Enter Project Name , Description and select the visibility of project and Click create button.
4.Click the Test Plans
5.Click the Load Test section
6.Click + New button and select Apache JMeter Test
7. Enter your load test parameters. To run your test near to where your users are located, select a closer location for your load test. Then start your test when you’re ready.
Where you can pass the multiple test data CSV files in supporting files field.
Note : For information about the scripts and supporting files used for JMeter web tests, see Build a Web Test Plan on the Apache JMeter website.
8. As the test runs, you see live information about the progress of the test. You can stop the test by using the Abort link on the toolbar.
9. When your test is done, look at the results to see how well your app performed. For example, you can see an overview of your app’s performance in the Summary page. This page shows all of the main metrics such as average response time, user load, requests per second, failed requests, any errors that might have occurred, and test usage.
The lower section of the Summary page shows the settings used for the test, and details of the five slowest requests during the test. If there are any transaction tests, the page will also show the five slowest of these. Use the Arrow icon above a column to sort the list based on the contents of that column.
10. Open the Charts page to see a graphical representation of the test results over time. The charts show the average performance, throughput, errors, and the results of each test request. Hover your mouse pointer over a chart to see more details.
11. Open the Diagnostics page to see detailed information such as a list of errors and status messages.
You can also use the -> icon in the Errors section of the Summary page to go directly to the Diagnostics page.
12. Open the Logs page to see a list of test runs. Choose the link in the Attachment column to download the detailed log as a text file.
13. If you have a favorite listener that you use to analyze results in the JMeter IDE, download the test results in .CSV format and the logs as a zip file from the Download Results link.
14. To run the same test again, choose Rerun.
JMeter Limitations with Azure DevOps
- Supported version of Apache JMeter is version 3.2.
- Currently, only HTTP samplers are supported.
- Custom listeners are not currently supported.
- Cannot use other app monitoring tools when load testing in the cloud.
- Don’t support Simple and transaction Controller
Categories: Out of Box
“Supported version of Apache JMeter is version 3.2” now is ver. 5.1 or higher … show how to run other method