We could quickly create a POC of complete end to end flow using postman and a similar POC for comparison purpose on JMETER. The main criteria for selecting the tool was to have an open source option which helps to quickly get started with the test automation task, is easy to use, gives a nice and detailed reporting and is easy to integrate with CI tool.
Mostly the team was briefly familiar with Postman, JMETER, rest assured and FitNesse tools/frameworks for API automation. Doing POC and Deciding on the toolĪ few months back when we came up with a plan to automate API tests of our application, first question in mind was, what tool to use which will best suit our requirement? Let’s now move to each phase one by one wherein I’ll talk about our project specific criteria and examples in detail.
#Postman script automation code#
By default, they are present in Java script but by using it you can generate code snippets in a variety of languages and frameworks such as Java, Python, C, CURL and many others. It presents you with a friendly GUI for constructing requests and reading responses, easy for anyone to get started without any prior knowledge of any scripting language since Postman also has a feature called ‘Snippets’. It allows for repeatable, reliable tests that can be automated and used in a variety of environments like Dev, Staging, and Production etc. Doing POC and Deciding on the tool depending on its suitability to meet project requirementīefore moving on to talk on these topics in detail, For those who are new to postman, in brief, Postman is one of the most renowned tools for testing the APIs and is most commonly used by developers and testers.Thus I have structured this blog into following phases: In the first blog of the series, we’ll talk about the phases till implementation while in the next blog we’ll discuss integration with Jenkins, monitoring etc. thus the content of these blogs is totally based on our experience and learning while setting it up in our project.
#Postman script automation series#
I am writing this two blog series to talk about end to end flow of API automation with Postman from deciding on the tool to implementing the suite till integration with CI tool and report generation. And once the tool is finalized, we have to design an end to end flow with the tool which is easy to use, and we can get most benefits out of automation efforts.
Although multiple tools for automating API testing are available and known to QAs, we have to decide on the tool that best suites our project requirements and can scale and run without much maintenance/upgrade while creating a test suite. This means it’s crucial to thoroughly verify APIs before rolling out your product to the client or end-users. Every application you build today relies on APIs.
0 kommentar(er)
