These days where Applications talk to each other using API, the verification of any message between the applications\/microservices needs to be verified. This checklist includes some best practices for API verification.<\/b>
\nJoin the DZone community and get the full member experience. Microservices are a designer’s way to address the complexity of applications in today’s world. Verification and Deployment of these applications are however lost in the implementation as the same thought the process is very rarely communicated in the Real-world. A web application that could be decomposed into Model-View-Controller architecture has morphed to the world of Unstructured Data Microservice Frontend. The ability to have a configurable backend(datastore as opposed to a DB) and a Flexible Frontend places Microservice API as a premier source of data interchange. This check is a work in process to the traditional tester\/validation team to address real-world challenges in the deployment of Infrastructure as Code. These are some guidelines that could be used to check the payload, response, deployment, and parameters from the YAML for the API to be tested. 1. Get the YAML or API specs listing the URL. i.e https:\/\/localhost:8089\/API\/Vx\/Resource 2. Confirm and verify the Method (GET\/POST\/PUT\/PATCH\/UPDATE) and URL to the server Deployed to ex: (https:\/\/:PORT\/) along with valid: A: credential with Bearer Token B: Parameters? XXKEY=XXVAL & YYKEY=YYVAL ( from the Path section) C: Body of the Method is well-formed ( from the Schema) and declared in the header 3. Verify that the API and API versions are deployed to for Testing 4. Check for Payload ranges for Min\/Max and Out of Range Values in the body of the payload 5. Check for REST API Response codes as listed on the YAML\/API 6. Match the Data on the UI with the GET\/PUT Body to match the value(s) displayed on the UI. 7. Check for Schema Error with Mandatory\/Optional fields in the API Body\/headers. refer[3] for Schema Validation. Opinions expressed by DZone contributors are their own.<\/p>\n