Day 1 - API Testing vs. UI Testing

This comment is generic which includes both UI and API test automation.

I know many start some kind of automation for web apps i.e., UI Automation. There are many open source and paid softwares available for the same using various technologies and programming in different languages. 

And many tools also allows record and play which may fit for some projects and many not be for some projects. And many expertise available in the domain as well thru various forums.

However, when it comes to API testing, and more evolving towards Microservices, this area is picking a lot know in the market.

But, for QA / Test engineers it is a bit challenge to test and automate the entire business flows as there is no UI for those who coming from web app testing. It requires data to be used from one API call response to the following request, data comparision as part of verification etc.

Either it needs complete programming skills( unlike web, no record and play possible here) to create some kind of framework.

Other demand is to be able to adjust for the Ajile model, do quick releases to reach market demand. 

Of course, there are tools available in this area too, but tricky to use.

Luckily, SmartBear has both free and paid products  which not only allows to test customer products, but also enabling the teams to automate their business functionality.