Automate a Jenkins CI/CD Pipeline with API Fortress
With a CI/CD pipeline, the work of distributed teams come together in an automated flow to build, test, and deploy new code. That means rewriting the rules of how releases are built and tested. One of the first things that the Jenkins wiki (Jenkins Best Practices) tells newcomers to CI/CD is that “unit testing is often not enough to provide confidence [of desired quality].” The wiki then talks about the necessity to automate API testing throughout the lifecycle to ensure that all distributed teams are continually working with good services and data.
Let’s take a closer look at those two stipulations of a Jenkins (or any) CI/CD pipeline:
- UI Testing Isn’t Enough: In our eBook, Nine Bugs That UI Testing Could Not Diagnose, we tell nine horror stories from real customers of API Fortress involving API vulnerabilities and bugs that UI testing did not detect early in the life cycle, or did not detect at all. The outcomes were loss of revenues, reputation, and increased threat of an API breach. Even simple API testing finds the vulnerabilities and bugs that UI testing cannot. Learn why in our presentation: Watching the World Burn: API Testing as an Afterthought.
- Run API Testing Continuously: CI/CD pipelines produce iterative releases so that services and mobile apps can evolve quickly without increasing the number of bugs or vulnerabilities released. Thousands of enterprises are trying to move from monolith to microservices/modern APIs, but face challenges properly incorporating their Jenkins CI/CD pipelines.
API Fortress was built from the ground up to solve these issues for the digital enterprises of today. Our new breed of API testing automation includes unique capabilities to standardize and collaborate across teams thanks to a platform architecture that can be deployed on-premises or cloud. This is good news for any enterprise that needs to strike the right mix of speed and quality concerning their new IT investments and initiatives.
How to Integrate API Fortress with Jenkins
1. APIF-Auto Command-Line Tool: API Fortress is an API-first platform with a robust set of APIs. To make life easier for our customers we created a command-line tool named APIF-Auto that makes it very easy to add a pipeline script and get results in JUnit format. To learn more about that setup you can read here.
2. Connect by API: API Fortress allows anyone with manager access to create a webhook, that can be easily called from within Jenkins. You can read the details on that here.
Advantages of Using the API Fortress with Jenkins
- Total Automation: Fire your entire test suite, or just some tests with specific tags, as part of your CI pipeline. Test in seconds what used to take days or weeks.
- Minimal Setup Required: Use the command-line tool or webhook to automate test execution in minutes.
- Flexibility in Workflows: API Fortress can execute tests stored in the platform, or from your chosen VCS. See those docs here, or speak to your API Fortress rep to learn more.
- Works with Any CI/CD: Thanks to APIs the platform is completely CI platform agnostic. If your organization changes to another platform such as Azure DevOps, TravisCI, or Bamboo, for example, the integrations are nearly identical and just as simple.
SECURE YOUR API TESTING RESULTS AND DATA
Deploy on-premises or hybrid cloud using our Kubernetes or Docker deployments. Or use our SaaS platform at apifortress.com. Get complete flexibility to allow your company to experience complete control over data and tests, with minimal setup headaches. Use Kubernetes or Docker
We invite you to sign up for a free trial and demo of API Fortress and put your testing to the test.