The company had four major needs – functional API testing, collaboration, integrating with CI/CD, and security.
“We had tools in place that were capable of a high-level look at our API environment, but little more.”
They had created a suite of tests that were failing to provide insight at the API layer. They have extensive selenium coverage, but it failed to go beyond front-end. It purely analyzed the GUI, and didn’t go deeper. The testing suite was unable to ensure schema compliance with regards to database queries.
“[We] needed something that allowed our QA team to interface with our Dev team for test creation.”
The development team also wanted to eliminate redundancies. They wanted their team to collaborate with the quality assurance team. The Dev and QA teams were creating similar tests independently. Creating a level of confusion about ownership, total coverage, and true contract validation.
“During the [proof of concept], we weren’t sure which CI/CD platform we were going with. We were looking at Jenkins and Bamboo.”
Their selenium suite was integrated with their current CI/CD process, and they wanted to add API testing to that process as well. To complicate matters they were moving from an existing solution to their Jenkins or Bamboo.
“We deal with a substantial amount of privileged information and we can’t risk exposing that to the outside world.”
Finally, being an insurer meant security was of the utmost importance. They wanted to find a way to be both secure, and yet collaborative.
THE RIGHT FIT
The team quickly realized their list of needs surpassed the availability of their dev team, and extending their internal suite to include API testing meant continuing down a path that was already showing its age.
API Fortress provided a containerized version of their platform using Docker. The fact that API Fortress exposes both the ability to execute tests and the ability recover test data via an API allowed the company to integrate it into their developing CI/CD process with ease.
“Our improved continuous integration and deployment flow was a major initiative, and the platform’s flexibility allowed us to sync it up with the rest of our testing suite.”
“API Fortress allowed us to integrate a robust monitoring platform without upsetting all of the other decisions we were making [with regards to] our processes.” The team gained a number of important benefits in bringing API Fortress on board. Not only are the developers and QAs able to cooperatively create meaningful tests, but these tests are run as a part of the CI/CD pipeline. API Fortress is currently configured to cause a CI/CD build to fail on a test failure, allowing the team to catch API issues before they go live.
“API Fortress allows us to deploy with confidence knowing we now have coverage from the API through to the front-end. We know exactly what to expect with each deployment, and we have reduced bad deployments by 45%.”