Simplifying API Testing at NCR

Simplifying API Testing at NCR Anton Hristov February 25, 2021

January 30, 2026 · 3 min read · API Testing

Simplifying API Testing at NCR

Anton Hristov
February 25, 2021

Yesterday, mabl found itsnew native desktop covering. The app centralizes and streamlines low-code trial mechanisation across browser, mobile devices, and APIs, making it easy for quality professionals of all cryptography levels to screen the entire user journey regardless of application complexity. & nbsp;

The new app was designed with feedback from the Friends of mabl community, including Eric Johnston, IT Business Analyst at NCR. Eric and his team are creditworthy for testing at the leading provider of banking and e-commerce resolution for fiscal, retail, hospitality, travel, telecom and technology industries. & nbsp;

As an early exploiter of the mabl desktop app, we went behind the scenes with NCR to understand how this digital payments elephantine sees API testing impacting package quality. & nbsp;

When API stands for “ A Pain In… ”

Modern engineering team embrace APIs as a foundational piece of application development, but regrettably, test them can be a complex labor that increasingly burdens lineament engineering teams. Quality quizzer, specially manual testers, have few ways to try API functionality outside relying on unnecessarily complex, code-heavy examination that require programme know-how to make and maintain.

For Eric and his team,API screenhad a few pain points. First, they didn ’ t have a tool that made API testing simple enough for non-coding team members to build tests, limiting their ability to try APIs and control sufficient trial coverage. Even when API testing was being make, the NCR team miss a individual position to fund (and execute) both browser tests and API tests, create it hard to garner visibility over their testing event. Finally, API examination was disconnected from browser trial since there wasn ’ t a way to connect API test data and browser trial datum. This meant that the team had to repair to repeat efforts across APIs and the browser every time they ask to test their application. & nbsp;

Early benefits of API testing with mabl

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Prior to API examine using mabl, Eric ’ s squad built API tests manually, but didn ’ t have the tools to fulfill them regularly. Though they know the value of API testing and its part in maintaining a sleek user experience, manual API testing was simply too time-consuming to execute on a regular fundament. Further complicating the challenge was that yet when API examination was complete, they didn ’ t have a reliable reporting mechanics in place to make test data actionable. & nbsp;

Since starting theirAPI testingjourneying with mabl, NCR is already seeing clear benefits of the new, integrated screen capacity. Currently, they have mabl using API test to give test information to browser tests using shared variables, as easily as execute functional validation on a sample set of APIs. But the benefits are already clear as API testing is very tight and honest, with near-instantaneous feedback that usually flags the source of the issue. & nbsp;

The faster, more accessible API tests offer an easy way to expand end-to-end exam reporting, enable the NCR team to unify API testing and browser testing into a single strategy with a unified dashboard that ensures testers aren ’ t replicate efforts and that the entire user experience is fully tested. & nbsp;

The road ahead for quality engineering

With early access to the new API testing capabilities, Eric has already been able to plan his test mechanization strategy around growing mabl acceptance, with the side welfare of using mabl as a learning creature to facilitate his team become comfortable with API testing. At this point, 20 percent of the NCR examine team is utilise mabl for API testing, with a plan in property to expand to the entire team. & nbsp;

As adoption grows, Eric conceive his squad can transmute their testing strategy to incorporate dailybrowser examination and API testto give quick, consistent feedback on the constancy of the application. Far from the disconnected, time-consuming project that API quiz was before mabl, NCR will be able to make API testing a quotidian and unproblematic machine-driven task that ’ s coordinated with the rest of their testing strategy through the low-code UI of mabl. & nbsp; & nbsp;

Want to join NCR at the forefront of integrated browser and API testing? Register foryour free trialof mabl today! & nbsp;



Quality Engineering Resources

Automate This With SUSA

Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts needed.

Try SUSA Free

Test Your App Autonomously

Upload your APK or URL. SUSA explores like 10 real users — finds bugs, accessibility violations, and security issues. No scripts.

Try SUSA Free