Open Source Projects - API Fortress

Open Source Projects

API Fortress is a continuous testing platform for APIs. As a true platform solution, we offer the flexibility to achieve many critical use cases that are simply not possible with other solutions. When needed, we create open source projects or “helper apps” to extend our platform’s capabilities. Find our helper apps on our GitHub page.

OpenSourceHero

Open Source Projects

3-Legged OAuth
Micro Gateway – AFtheM
HTTP Logger for Kong
GAEL – API Elements Parser
Database Helpers – DB to APIs

3loa
For: 3-Legged OAuth Automation

Found here: https://github.com/apifortress/3loa

The 3loa helper is an open source application that automates 3-legged OAuth 2.0 flows. By simply integrating the 3loa Helper with API Fortress (or any platform), developers and test engineers can test and validate flows that include an authentication flow that requires human interaction.

API Fortress Micro Gateway – AFtheM
For: Mock Recording and Watchtower

Found here: https://github.com/apifortress/afthem

AFtheM “API Fortress the Mediator” is an open source, Scala / Akka based, asynchronous API micro gateway. The purpose of this helper application is to provide a highly modular gateway for API calls to help developers, QAs, and data scientists:

Capture
Measure
Transform
Filter
Simulate

The processing engine can also be modified for your unique needs. This application was built specifically to aid with the mock recording feature of the API Fortress platform. In the near future, it will also be a key component in the API Fortress Watchtower platform, which powers AI-driven API testing.

AFtotheM

HTTP Logger for Kong
For: Mock Recording

Found here: https://github.com/apifortress/fortress-http-log

The goal of this plugin is to help with mock recording. The plugin itself is for the Kong API Gateway, and facilitates capturing complete HTTP requests and responses (including the request and response bodies if required) as they transit through the Gateway. Once this data is captured, the plugin will send the data to a specified endpoint via HTTP (eg: API Fortress).

APIF_FlowChart_MockingWithKong-800x600

GAEL

Found here: https://github.com/apifortress/gael

GAEL (Groovy API Elements) is a parser for API Elements written in Groovy. The purpose of GAEL is to simplify the use of API Elements descriptors in your Java/Groovy projects. Using a versatile and extensible structure, it provides wrappers with utility accessors and safe query functions that allow you to deal with the variability of the contents.

File System and Database Helpers
For: Transform a DB/Folder Connection to an API

Found here: https://github.com/apifortress/helpers

These Mule flows (for the MuleSoft ESB) are a pair of open source applications designed to make accessing your databases and folders easier. The applications (one for DBs and one for folders) make your DBs and folders accessible via an API. This allows you to easily pull in data from these endpoints into your tests for use as inputs and more.

DBtoAPI_1

Want to add API testing to your workflow?

Schedule a demo or get a free quote.

Schedule a Demo Get a Quote

Blog

Automate a Jenkins CI/CD Pipeline with API Fortress

October 9, 2019

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.

95% of API Breaches are Caused By This - Yet Few Test for It

September 24, 2019

Nordic APIs wrote a great article, with input from industry…

UI Testing is Not Enough

September 19, 2019

“Our UI Tests Hit the APIs” This is a true statement. It’s always true when you are doing things such as testing native mobile applications, for example. The problem is that it implies something that isn’t true. It implies that APIs are then being tested, which is not the case.