By incorporating load tests into your CI/CD pipeline, you can detect and address performance issues early in the development cycle. This approach lets you identify and fix potential bottlenecks before they impact your users, saving time, effort, and costs associated with addressing performance problems later in the development process.
To add BlazeMeter load tests to your CI/CD pipeline, you need the following:
SCM: A source code management system. This is where you keep and version your application’s source code. The SCM can also be used to version your test scripts and most companies do so. Most popular SCM tools are based on Git.
CI/CD: A Continuous Integration and Continuous Delivery toolchain. CI/CD tools are used to build, test, package and ship your application to production. They offer multiple integration options as plugins and scripts to integrate with a huge ecosystem of tools. You need to have Taurus CLI available in your CI/CD runner/delegate because we are going to use it to trigger a BlazeMeter test.
BlazeMeter: A leading Continuous Testing solution.
Including BlazeMeter load/performance tests in a CI/CD toolchain involves two steps:
1. In your CI/CD tool, you create a step to clone the git repository where you keep your test scripts (JMeter, Gatling, Taurus, and so on).
2. In your CI/CD tool, you create a step to execute a Taurus CLI command (Bash script). This step uploads to BlazeMeter the test scripts you downloaded in the previous step and then triggers the test. In the background, Taurus CLI uses BlazeMeter’s REST API to update the test scripts and trigger the test. It also passes or fails tests according to the failure criteria you define in BlazeMeter.
Note: BlazeMeter keeps the script it uses for each test run so you can confirm it was the right one.
0 Comments