This post will specifically address team support of the Jenkins-RedLine13 integration. This integration with Jenkins means that you can build, deploy and load test your project continuously with Jenkins individually or as part of a team. We call this Automated Testing with Jenkins – Team Support.
We’ll then talk about how a RedLine13 customer is doing this today.
Setting up your Jenkins-Redline13 Integration
If you haven’t set up your Jenkins-Redline13 integration, here are the instructions to build, deploy and load test your project continuously with Jenkins.
If you are interested in executing different test types with Jenkins and RedLine13, this post is a deeper dive into Jenkins and RedLine13 and a look at executing different test types with Jenkins and RedLine13.
Continuous Integration and Continuous Delivery (CI/CD) is a convenient way to build and test your application. Jenkins, one of the most popular open source tool used to perform CI/CD tasks, can also be used to schedule load tests on RedLine13.
Automated Testing with Jenkins – Team Support
With a team account (Premium Subscription) on RedLine13 sharing your test plan to all members of your team is automatic. And once the team has access so will your Jenkins build job, making it easy to share to your CI/CD process.
Here’s what it looks like. First save a test in RedLine13 as a template for Jenkins:
In Jenkins, the RedLine13 integration includes a drop down:
And it will show all your ‘templates’. It will include your templates and templates from anyone else on the RedLine13 team. This is critical as we’ll discuss later. Here is the list of all templates:
And it will show all your ‘templates’
Jenkins-Redline13 Integration User
Infutor is a RedLine13 client that uses the Jenkins-Redline13 integration. Infutor is a leader in identity management, enabling brands to instantly identify consumers and make informed marketing decisions.
The Jenkins-Redline13 integration for teams was important for Infutor because they have a small committed QA team of 5 members moving from one project to another. Sharing information and test plans helps them do more. For Infutor, collaboration is key. They need that because one test configuration has to be visible and available for the rest of team in order to have hot swap resources. And in 2020 they are moving to CI/CD (Continues Integration/Continues Delivery). Jenkins-Redline13 integration where each member can see each other’s template and modify it is paramount in DEVOPS.
Infutor moved from standalone to cloud. At the beginning they thought that what they were stressing was the server hosting JMeter instead of the target API. Another plus is to be able to hit different AWS regions across the US. They increased collaboration, having all testers on the team and hot swapping resources for continuous measuring. Just clone and GO!
Redline13 has been a great tool for measuring our API and tracking performance on every sprint. We use the Premium version which gives us the insight we need and helps us to publish results quickly.
Roberto Valverde, QA Manager, Infutor
Now you know what to do to have Automated Testing with Jenkins – Team Support.
You can try your own test, whether it is simple or integrated with Jenkins, on RedLine13 for free.