Here is what I look when I'm exploring to learn an end point of web API for first. I'm talking of the Web API that uses HTTP protocol.
- What is the purpose of this end point?
- How it helps and to whom?
- Who uses this end point?
- Identify the host of the end point
- Identify the path of the end point
- Identify the API's end point
- Identify the version of the end point
- Know the different version that are available for an end point
- What are active?
- What are inactive?
- Who are the consumers using these different versions of this end point?
- What's the difference between these versions?
- Identify the HTTP method of the end point
- Know the different HTTP methods this end point supports
- Identify the resources the end point interact with for CRUD activity
- Know the HTTP Request headers it needs, uses and good to have
- Know the HTTP Request payload or data and its format
- Know the HTTP Response headers and good to have
- Know the HTTP Response Status Code and what actually it should be returning
- Know the HTTP Response content and format returned
- Does this end point enforces any contract with the consumer?
- Know the intent of your test on this end point
- One test in one request is useful unless the context demands otherwise
- Is there anything cacheable in the end point's response?
- How the request payload is?
- How the response payload is?
- What is the language in which the end point is written?
- What is the language in which the resources that end point updates is written?
- Any framework used to build this end point?
On learning this, I continue to next phase in exploring and knowing the web API.
No comments:
Post a Comment
Please, do write your comment on the read information. Thank you.