In this race to win and retain customers, we forget that a critical aspect of developing trusted apps is by incorporating effective testing strategies. Continuous testing as part of the CI/CD pipeline is the need of the hour.

Are you curious and wondering :

1. Why should I worry about API Testing?
2. How to ensure testing doesn’t play catch up to a rapidly growing code-base?
3. How do we adopt a test-driven development approach?

This white paper can help you find answers to these questions. It focuses on how automated testing can help you build reliable APIs. It also elucidates how effective monitoring of APIs in the production environment can help you develop trust among your consumers.
Dive deeper to know how API Connect Test and Monitor can solve quality at speed problems through continuous testing.

https://www.slideshare.net/SwethaSridharan3/can-you-trust-your-apis-white-paper-on-api-testing

Can You Trust Your APIs? was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

Are you wondering how you can use Test & Monitor to leverage testing secured APIs?

It is simple and easy, you can do that in no time. Don’t believe me?

Check out this quick video to understand how you could do this-

Test & Monitor APIs secured with OAuth was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

With API Connect Test & Monitor collaborating with your team has never been so simple. You can invite your team to Project folder where you can all work together in a shared workspace like a Github repository with simple steps

1. Login to “My IBM” dashboard at https://www.ibm.com/myibm with your IBM id.
2. Look for API Connect Test and Monitor offering.
3. Select Manage Users option from Manage button
4. You will then have the option to add new users as a License User.

Now you are all set!

Check out a quick demo here

Collaborate with your team in no time was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

We build the best API security and lifecycle management software on the market.¹ It helps developers and businesses secure, manage and share their APIs, to scale their businesses and meet the needs of their customers everywhere. Indeed, these days developers and enterprises face significant challenges in their API management efforts, and these are compounded when they seek to test and monitor those APIs. As such, we also develop API Connect Test and Monitor, an automated, collaborative and powerful API testing tool, to assist with the many APIs they create.

“According to a One Poll study, businesses on average manage 363 different APIs, and two-thirds (69 percent) of those organizations are exposing their APIs to the public and their partners. …”

-Torsten George writing in Security Week

With the speed and complexity of modern business, protocols, standards and languages, there’s multiple risks to not keeping up. If a provider does not offer APIs that meet the security requirements of their consumers or own organization, they may end up harming their customers and end users. Examples abound from Panera to Facebook even Google can slip up in these ways. This emphasizes the importance of an API Platform that can help secure, manage and share APIs in a secure and scalable way.

As if the security challenges weren’t enough, the ability to provide information to API consumers in an understandable format is also essential. Specifications such as Open API, RAML or API Blueprint help to improve this through their guidance and standardization. However, Though Open API Specification seems to have won out as the premier specification format over RAML or API Blueprint, there are still subtleties that many API Providers need to be aware of.

With industry-specific coordination and work to converge on standards, it can be very confusing to align on which of these formats are important to invest in. For example, when the European Parliament adopted a revised Payment Services Directive (PSD2)they underlined the need for banking enterprises to offer APIs in a standard method to allow developers to deliver new experiences to their customers in a secure and scalable way. Likewise, efforts in the telecommunications and healthcare industries are driving further openness without sacrificing security.

To help get our customers started we’ve provided the API Connect Test and Monitor Marketplace a reference of some key API Standards. We picked some of the API standards around which we’ve seen customers of ours begin to align. We’ve provided example pre-formatted tests for APIs of these standard formats in a way that our customers can easily grab and get started. Additionally, these can be customized and set up as a recurring monitoring call within API Connect Test and Monitor. We started with two important industry standards:

Banking and Financial:

Banking Industry Architecture Network (BIAN) is an organization set up to establish and promote a common architectural framework for enabling banking interoperability.

Communication:

TM Forum is a non-profit industry association for service providers and their suppliers in the telecommunications industry. Members include communications and digital service providers, telephone companies, cable operators, network operators, software suppliers, equipment suppliers, systems integrators and management consultancies. Amongst other tools, they provide REST based Open APIs to help its members in their digital transformation initiatives.

We look forward to helping you meet your goals as you move toward a more secure and open, controllable and scalable world where your customers can build on your successes. As a start on that we’ve not only provided the market-leading platform to secure, manage and share your APIs, but a great way to Test and Monitor them too! We’ve further helped to reduce some of the confusion and uncertainty by providing some reference tests for API Standards that have gained momentum. As technology continues to evolve our team will continue to look for new industry standards that could be helpful to our customers and offer them as well.

Check it out and let us know what you think!

(1) By “ Best” I mean

A.) — the largest market share and thus greatest trust (IDC Market Share Report: We are #1, double of our closest competitor. https://developer.ibm.com/apiconnect/2018/08/08/ibms-api-management-undisputed-1-market-share/)

B.) The best rated by industry Analyst Forrester, https://developer.ibm.com/apiconnect/2018/10/29/analyst-firm-lists-ibm-api-connect-as-an-api-management-leader/

and

C.) the most delightful user-experience given our Award for Design. (iF design award — https://developer.ibm.com/apiconnect/2019/03/05/ibm-api-connect-wins-2019-if-design-award/)

Announcing the API Connect Test and Monitor Marketplace was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

Why?

In software, we always have a user that we are serving. Our software exists to do some job for that user. We expect that the software we’ve created will do that job effectively for that user, that it will make their life easier or more effective and that it will not make their life harder.

At API Connect our why is to create software that allows API providers to make their APIs secure and open so that their developers and customers can build on their creations and unleash their own value for the world.

As we see the world there are two kinds of people: API Providers and API Consumers. Those API Consumers are the people our customers, the API Providers exist to serve.

One of my specialties is in API Connect Test and monitor. This is software that helps API Providers see the world the way their API Consumers do.

API Connect Test and monitor allows them to simply call an existing API from their cloud account, get a response and from that automatically generate a test with no code. They can then edit that test visually or in code and can publish it and set it to run on demand with deep, detailed output on their API quality. They can further set that test to run as frequently as they need to in order to understand how their own APIs look to their consumers. They can test the success and failure conditions, the latency and the detailed expectations of the payload of a response.

They can truly inspect what they expect from their APIs.

I was fortunate to get a chance to present about how inspecting what you expect is important both in the military and with APIs at the Nordic APIs Austin API summit. If you’d like to check out the slides or the video of the presentation you can do so. But if you’d rather just dive in and try it out for yourself, you can get started with a free account today!

……

P.S. Do you want to learn more about what Product Leaders might learn from military veterans? You might enjoy The Art of Product War

Inspect what you Expect! was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

To configure a basic API Connect environment, here are the basic setup

• Configure and set the mail server
• Configure gateway services
• Configure portal service
• Configure analytic services
• Invite a provider organization owner
• Organization owner accept the invitation and create an organization
• Login to organization
• Create a draft API
• Publish a Product to Sandbox

We need to input many fields and many clicks to manual setup via the UI.

Simplify with API Connect Test and Monitor with a Project

Automate the configuration with 3 main steps

1. Set up the configuration environment variable file
2. Set up the Test scripts with configuration flow
3. One Click to run the configuration

Setup configuration Variables

Set up your Configuration Flow

Run your configuration

You can even schedule a run regularly.

Dashboard to check status

Summary of Usage

• Perfect for configure environment with bootstrap data
• Reports generated for configuration issue
• Basic bootstrap smoke test

Test and Monitoring http://ibm.biz/apitest

• Statistic generated for monitoring
• Details reports

Originally published at https://medium.com on April 29, 2019.

CLICKS, CLICKS GO AWAY was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

It has been a fast-paced four months as a Full Stack Developer co-op as RBC transforms its digital strategy. As part of this transformation, Business Financial Services (a team within RBC) has been gravitating towards implementing microservice architecture to better handle load from 800,000+ clients daily.

What are microservices? Microservices are small applications where each service serves a specific purpose. The microservice architecture champions modularity, which in turn improves scalability. More instances of specific services can be spun up as load increases, as opposed to spinning up more instances of a monolithic application needing several times the resources of each microservice.

As BFS implements microservice architecture, several problems have surfaced. With hundreds of microservices projected to be created within the next few years, it becomes a huge task to keep track of the URL of each microservice, especially considering application movement between developer environments (dev, QA, production). Furthermore, BFS uses Bluemix and other hosting platforms to serve its applications, meaning load balancing cannot be centralized or delegated to a single platform. Bluemix also doesn’t provide fine-tuned health checks, meaning unless your instance has crashed Bluemix will continue routing traffic to it. Finally, Bluemix only routes traffic to instances on Bluemix, which limits our hosting platforms to just Bluemix.

The Solution: Microservice Magic!

Solving these issues is Eureka. Netflix released Eureka in 2012 as their solution to the issues that arise with using the microservice architecture. Eureka works like a phone book; when a service is spun up it registers itself with Eureka, providing its URL and how other services can connect to it. Most importantly, it fetches the latest copy of the microservice registry from Eureka. This registry is updated as services go up and down, and all microservices receive the changes. When a microservice needs to connect to another, it finds the URL of the service in the registry and makes the call. Furthermore, even if the Eureka server is unreachable, all the microservices still maintain the latest copy of the registry and can continue working.

Within BFS, several teams use Angular for the front-end and Java Spring Boot for the back-end. Spring Boot includes support for Eureka natively, so Eureka server setup is as easy as including the dependency and spinning up the application as a standalone Eureka server. Setting up microservices to be Eureka clients is easy as well with Spring Boot; simply include the appropriate client dependency and set the Eureka properties to connect to the correct Eureka server.

Once a Eureka server and clients have been made, the microservices are ready for calls to be forwarded to them. In the UI, REST calls need to be forwarded via another Netflix open source project called Zuul. Although a “phone book” has been made (Eureka), the UI needs a service to query the Eureka server which returns the appropriate URL. Zuul provides this functionality. Think of Zuul as a reverse proxy; Zuul takes a service ID matching the one found on Eureka and returns its appropriate URL. In the application properties file in the back-end of the UI, properties can be specified to proxy all calls made to a certain slug to a corresponding service. For example, the back-end portion of the UI can be configured to forward all calls from /my-example/** to the service ID my-api, with the path parameters ** being forwarded to the service as well. Zuul uses Eureka to fetch the registry of services’ URL, and setup in a Spring Boot application is like that of a Eureka client — include the dependency, add an annotation and a few lines of code, and your application is ready to forward requests via Zuul!

Now we have a server which stores the registry of all microservices registered on it, and clients can connect successfully to each microservice individually. But what about microservices talking to other microservices? Say we have an API handling all calls related to where a certain make of car can be purchased, and another API handling the current price of those cars. How would those two microservices be able to talk to each other?

A third open source solution that Netflix introduced is called Ribbon which allows for communication between microservices through Eureka. Zuul was introduced above as a reverse proxy, but it serves the outward facing part of routing. Ribbon is the inward facing part. Ribbon serves as a routing layer between microservices; it fetches a list of servers each microservice is running on and uses the registry from Eureka to populate different client contexts. Having a routing layer increases modularity by allowing the user to address concerns such as security and logging and abstracting away from core API code. Again, setup is as simple as the process described above in Eureka and Zuul.

With this many microservices in play and many more planned, API testing and monitoring becomes ever more important. With hundreds of thousands of clients leveraging our software and services, it is crucial to thoroughly test APIs before they go live to ensure stability. As microservices often rely on one another to produce an expected result, it’s also critical to monitor the health of each microservice and determine if certain designs need to change to optimize resource usage.

Overall, the microservice architecture at RBC has improved modularity and allowed us to scale quickly with minimal effort to the developer. Microservices promote abstraction, and separating logic in a way that makes sense. These four months at RBC have been fantastic, and I can’t wait to see the advances happening in the API ecosystem as a result of the microservice architecture becoming more and more prevalent.

On a last note, I’d like to include a special thanks to Tobias Coetzee, Senior Engineering Manager of Platforms & DevOps at RBC, for his time and contribution to the creation of this article, as well as his continued support of the co-op team here in BFS. I want to thank my team, managers, and the executive team as well for their passion for fast-paced learning and growing in the short four-month co-op term at RBC. If you’re interested in learning more about microservice architecture, there is a fantastic video available here which goes in depth about Netflix’s use of Eureka and the microservice system. Another interesting read is Martin Fowler’s take on microservices available here which discusses the recent surge in popularity of microservices.

Stay Ahead 📈

API testing and monitoring — start free-forever here: ibm.biz/apitest

We hope you found value in this article. Special thanks to Brian Lin for sharing. Please let us know in the comments what you would like to see next time!

On the Use of Microservices at RBC was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

Consumers want to “own” their dataーbut for business it’s a different story. By keeping your data private and not allowing your other platforms to process and analyze your data, you may lose out on competitive advantage in your industry. Additionally, you may lose a lot of productivity from not making your data easily accessible via APIs. Of course, working in a competitive industry may mean your data is your competitive advantage, but for many businesses, opening up your data to the world means more users and customers can interact with your business.

Eliminating Data Entry or Copying and Pasting

Nothing kills productivity like having to manually enter data into a spreadsheet or some other tool for analysis. Copying and pasting data from one source to another means there may be duplicate data and discrepancies between sources. One of the core tenets at Coda is giving our makers the ability to build apps, and one of the building blocks for this vision is connecting other apps makers are already using with their Coda doc.

We do this through…you guessed it…APIs. Everyday apps you use at your company like Gmail, Google Calendar, and Slack can be integrated with a Coda doc. This means your latest meetings from Google Calendar can be pulled into a doc for further analysis, or new meetings can be scheduled to be pushed to Google Calendar. The key point here is that there is no copying and pasting or manual data entry because your data on other apps is automatically synced with your Coda doc.

Context Switching Kills Productivity

There are numerous reports and studies about how multi-tasking is not actually that great for productivity. Let’s say you are trying to share a table you created in Excel with your team at your company. A common way of doing this might involve the following:

1. Copy the table in Excel
2. Open up your Outlook or Gmail application
3. Create a new e-mail
4. Paste the table into the message of your e-mail editor
5. Notice some of the columns are too wide, or formatting didn’t flow through, so you edit the formatting in Excel a bit
6. Repeat steps 1–5

By using the Gmail API in this scenario, you can take care of the formatting, e-mail composition, and even the sending of an e-mail in a different surface without having to “launch” the Gmail application. The steps above are for one of many workflows you may encounter at your company, and the APIs for various applications allows you to mix different applications together. For Google, creating the Gmail API is a key strategy for getting more users and developers using Gmail. A whole cottage industry for helping you connect different APIs together makes it dead simple to automate your workflows. Read Coda’s perspective on connecting your data together via Coda Packs.

Open Data Encourages Innovation Within Your Community

Coda also decided to create an API to give users the ability to further connect their apps and data together. Innovation happens when your community has the tools it needs to build libraries that would not exist if your data sat behind a paywall.

For instance, a community member built a PHP library utilizing the Coda API which allows people to access data from their docs in web development projects. There hasn’t been a use case for a Coda doc to act as a backend for your website or CMS, but with this library, it becomes a reality. Libraries built by community members are also open source so anyone can submit issues, feature requests, and contribute to the project.

What about connecting data with the physical world? Node-RED is a programming tool created by the IBM Emerging Technology team that gives users the ability to connect APIs with hardware. This tool is primarily used for IoT use cases, but the community has found interesting ways to wire together workflows.

A Coda community user also found the need to build a library that connects their Coda docs with the Node-RED tool, and created this library to solve this problem. Furthermore, the user created a package on npm, the most popular package manager for Javascript to make the library more accessible.

Conclusion

Through the above two examples of two users innovating with an API that was open to the public, more connections can be made between different APIs that did not speak to each other previously. What was the ultimate goal? To increase productivity, automate workflows, and encourage others to build and innovate in new ways that were not possible before.

Building and testing APIs should also be a seamless and automated process. I already showed that IBM is innovating with the Node-RED tool as it allowed members in our community to build other amazing tools.

It is critical to use tools such as IBM’s API Connect Test and Monitor that makes testing and monitoring APIs dead-simple. It requires zero code and removes a lot of the manual work that is typically required with other tools.

API Connect Test and Monitor is free-forever — get started: http://ibm.biz/apitest

Increasing Productivity By Opening Your Data with APIs was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

Blockchain

By now the distinction between crypto-currencies and blockchain technology itself is fairly easy to make. Cryptos like Bitcoin and Ether are tradeable tools with an associated financial value, similar to a stock for a company. Blockchain is the technology behind crypto that allows it to offer the benefits that consumers enjoy. It allows for traceability, security, and transparency driven by a trust in the technology itself. In brief, blockchains are an append-only, immutable ledger (database) that is distributed among all the parties of a network (decentralized). They’re great for some businesses and not useful for others. Blockchains are great for processing transactions, removing intermediaries, tracing products through a lifecycle and maintaining security. It has major implications on the finance and audit sectors, and supply chain management is also seeing rapid adoption with IBM and Walmart leading the charge with their most recent announcement of the Food Tracking Blockchain.

APIs

Think back to when you were learning trigonometry in high school. Sine, cosine, and tangent were all terms new to you but your calculator could readily solve the math problems with ease. At the time you were just concerned with getting your answer and may not have cared how the calculator was able to output answers as fast as you could input them, but the same thing the calculator did for you then APIs do now for developers (kind of). APIs are commands, protocols or other forms of communication that define how other developers can interact with a company’s software. They remove the need to write code from scratch and allows problem solvers to focus on solutions and rely on their community for help in commonly used functions. The API you’ve interacted with most often is likely to sign up or sign into an app using your Facebook or Google which call the appropriate sign-in APIs for those services. In short, APIs allow for communication between two otherwise separate applications and this is what makes them a great fit for blockchain.

APIs are already used on all blockchains because they make coding of functions much easier. However, with the rise of interest in blockchains, there has also been a rise in suppliers of blockchain technology as well as massive open source platforms for APIs and blockchain like the Hyperledger projects. So it is important for businesses looking to make their own blockchains or at least use one in their business to understand some of the key technical factors (like APIs) that go about making the technology possible and why they work so well with blockchain tech.

APIs and Blockchains

Essentially, APIs are processing large volumes of transactions to respond to client requests to access the data libraries of the API. So they need a database to store the data that will be accessed, they need to validate a client to ensure they have the permissions to access the data and they need to this fast. The primary benefit APIs gain from blockchain across these three categories is increased security across the full value chain.

APIs benefit from blockchains as a database because they can store data more securely than traditional databases can and their immutable nature makes them tamper proof while processing large volumes of transactions. Blockchains gained their popularity from Bitcoin, which relies on processing large numbers of transactions and blockchains, in general, are primed to handle large datasets. When APIs are used with blockchain technology the core functionality of APIs stays the same (accessing information from a database) but a database on a blockchain addresses the key security issue of potential hacks. Often the data stored on these ledgers is subject to privacy laws and organizations must take appropriate measures to prevent their users' data from being misused. Think back to the example of the Facebook Login API that most people are familiar with. How many services use that API and how many people would be affected by a security flaw?

Blockchains use top tier encryption algorithms to encode all data to prevent any tampering. For example, to hack into a blockchain using SHA256 encryption (like Bitcoin) one would have to compute a 32 character case sensitive password in less than 10 minutes (the time it takes the system to update), a feat currently impossible. The decentralized nature of blockchains also means that no one computer on the network can force an update without reaching consensus with the entire network. So the data that gets manipulated on the blockchain by an API will be more secure and more accurate resulting in more consumer trust in the organization.

Client validation on a blockchain works very similarly to how it works now. Clients have a unique digital signature on the blockchain, similar to a username, which tracks their actions and validates their requests to ensure the right person is accessing the API. Similar to the database application, APIs benefit from greater trust when validating clients on a blockchain due to increased security and transparency. Anytime an API makes a call, a digital trail will be left on the blockchain that can be used to trace all actions of any client on the chain to enhance accountability and ensure with a greater degree of certainty that the right people are accessing the right data.

Considerations

One current drawback of blockchains is their append-only nature, meaning that once a block has been created it cannot be changed. Data can only be added to a chain, not removed or adjusted. This can make mistakes extremely costly, especially if there is a flaw in the API making an automated call over a large volume of transactions. However, a permissioned structure like the Hyperledger Fabric allows key stakeholders to overwrite transactions if needed. This can be time-consuming relative to a traditional database but is still exponentially more secure. To prevent this APIs need to be perfect before implementation.

The only way to have perfect APIs is to comprehensively test your APIs in their intended functions using an API testing tool. Using IBM API Connect Test and Monitor save developers +95% more time when testing and monitoring their APIs. It does this by building in comprehensive testing scenarios automatically with zero code. This allows them to conduct more rigorous API tests more frequently. As the second half of the name implies, API Connect Test and Monitor can also schedule tests to run automatically. Routinely automated tests are important because as the data your API has to work with changes, so can the results. Furthermore, if you are regularly building up your API and changing the code itself then that needs to be tested often to ensure proper functionality. Failed tests automatically notify the appropriate person/team and all tests are saved in a suite for analysis when needed. Once your API works like it should with no errors then it is ready for your blockchain.

API Connect Test and Monitor is free-forever — get started: http://ibm.biz/apitest

Official IBM blog: https://developer.ibm.com/blogs/blockchain-api-testing/

What Does Blockchain and API Testing Have in Common? 🔗 was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.

The SaaS business model is an on-demand software delivery mechanism allowing the users to access the software via a web browser and pay for it on a recurring basis. The SaaS business model touched the $10B revenue back in 2010 and is expected to grow to $117B by 2021.

The explosive growth of SaaS economy is driven by several factors such as lower operational cost, maintain a consistent feature set, reduced time for setup and training, availability of multitude of cloud infrastructure that are cost-effective as well as support various architectural designs, ability to access the software on a variety of devices and many more. In fact be it a vertical such as healthcare, finance, real-estate etc. or horizontals such as HR tech, sales, CRM, marketing etc. companies today plan to aggressively expand their SaaS offering and move towards the on-demand software delivery mechanism with a subscription pricing model which can present a predictable revenue growth pattern.

The pivot to a platform business model

With the growing demand and hyper-competition to stay ahead of the curve and deliver incremental value to the end-customers, organization’s today are forced to innovate, achieve rapid time-to-market and explore new avenues to generate revenue. There are several mechanisms to build new business models within the product, however, lately with the understanding of the platform economy and popularization of API’s (application programming interface), business have found it much easier to build partnerships, create an eco-system to not only deliver a slice of the overall value but to expand the overall offering to a full-stack nature.

For e.g. a simple lean/kanban process management tool like Trello has now evolved into a SaaS that can integrate with google drive to manage documents, slack to foster improved and effective communication and Jira to ensure tracking of development tasks. This wouldn’t have been possible without the availability and easy integration opportunities with similar other platforms. In turn, from a user standpoint, it offers a single point of entry to a software which now hosts the complete eco-system for managing software development and eliminates the hassle to manage software fees separately for each of the integrated products.

Another great example from my personal experience in the e-commerce industry has been managing an API platform which allowed one of the leading American retailer to expand into reward-redemption, penny auction and incentives type platforms thereby opening up a new revenue channel. The API platform allowed us to share the product catalog, manage ordering experience, provide real-time inventory availability and finally the checkout and delivery information to external partners so that their customers can purchase the product easily without leaving the partner’s website. This pivot from SaaS business model to a platform business model or just opening up a new revenue channel wouldn’t have been easily possible without having API’s that can be accessed by developers and allow easy integration between different parties that deliver a part of the overall value to the end customer but have the potential to collectively delivery a much greater experience.

All things API

Managing an API based platform though comes with its own set of processes which involves designing, developing, testing, publishing, and versioning of the API’s. Until recently, not many tools were available which provided an intuitive interface for developers as well the API teams to manage the overall interaction and ensure successful and guided usage of the published API’s. Additionally, some of the common challenges include API bench-marking/performance testing, ensuring the right API usage pattern, testing of negative scenarios where the client systems are no more conducive towards the API etc.

From a test team perspective, how do they effectively manage API test beds, smoke tests, and regression scenarios? Also, on-boarding and training of a new member in the test team can present significant challenges and quite extensive efforts. All these can be effectively managed using the IBM Connect Test & Monitor tool. This tool is sure to improve the quality of the API since a developer can easily create automated tests that can be integrated with your CI/CD tools (think Jenkins) and hence save the hassle of either reverting the code or breaking something in production unknowingly.

Transforming SaaS to a Platform Business Model was originally published in API Connect Test & Monitor on Medium, where people are continuing the conversation by highlighting and responding to this story.