โ๏ธ ๐ฃ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ - ๐ฆ๐๐ฎ๐๐ฒ๐บ๐ฒ๐ป๐: There are several # of backend API's that are built and linked with the on-premise database and have been migrated onto the cloud. These are being built using the micro-services architecture. As an Automation Enginner you have to verify that API'S are successfully migrated.
๐ช ๐ฃ๐ฟ๐ผ๐ฏ๐น๐ฒ๐บ - ๐ฆ๐ผ๐น๐๐๐ถ๐ผ๐ป: So in-order to solve this problem first we have to identify how many services that needs to be tested? and with in each service how many API's that are being built? and with-in each API how many different end points it has?
Lets take an Considerate Assumption:
- # of Services that needs to be tested: 10
- # of API's that Exist with in the service: 10
- # of End points with in an API: 10
๐ ๐๐บ๐ฝ๐ผ๐ฟ๐๐ฎ๐ป๐ ๐๐ฟ๐ฎ๐บ๐ฒ๐๐ผ๐ฟ๐ธ & ๐๐ถ๐ฏ๐ฟ๐ฎ๐ฟ๐ถ๐ฒ๐ ๐๐๐ฒ๐ฑ:
- RestAssured
- TestNg
- BDD (Gherkins- Cucumber)
๐ ๐๐ผ๐ฟ ๐ฟ๐ฒ๐ฝ๐ผ๐ฟ๐๐ถ๐ป๐ด ๐๐ฒ ๐ต๐ฎ๐๐ฒ ๐๐๐ฒ๐ฑ:
- QAF
๐ ๐ฆ๐ถ๐น๐ฒ๐ป๐ ๐๐ฒ๐ฎ๐๐๐ฟ๐ฒ๐ ๐ผ๐ณ ๐๐๐๐ผ๐บ๐ฎ๐๐ถ๐ผ๐ป ๐๐ฟ๐ฎ๐บ๐ฒ๐๐ผ๐ฟ๐ธ:
- RESTful API Support
- Gherkin - Cucumber BDD sUPPORT
- Configurable API endpoints from a separate config file
- Cross-Environment execution feasibility
- Parallel test case execution feasibility
- Retry Mechanism in case of failure (Configurable)
- Test Suite Management (Configurable)
- API vs API comparison (JSON Payloads & Responses)
- Response Code Validation (Source vs Target)
- Response Body [Data+Attributes] Validation (Source vs Target)
- Response Code Validation (Source vs Target)
- A concise html test result report yielded as Extent Report
- Test Results email as an attachment to desired audience via AWS SES (Simple Email Service)
โ ๐ฃ๐ฟ๐ฒ-๐ฅ๐ฒ๐พ๐๐ถ๐๐ถ๐๐ฒ๐:
- Editor: Intellij
- Language: Java
๐ฒ ๐๐น๐ผ๐ป๐ถ๐ป๐ด & ๐ฆ๐ฒ๐๐๐ฝ ๐๐๐ถ๐ฑ๐ฒ:
โ ๐ ๐ฎ๐ถ๐ป ๐๐ ๐ฒ๐ฐ๐๐๐ถ๐ผ๐ป ๐๐ถ๐น๐ฒ๐:
- BaseApiTests