We started using postman for our API documentation. We have pulished our API documentation to Postman public network.
Sunbird-Knowlg
We have mulitple micro-services. We just started documenting for one of our service called DIAL.
We end up with strage problems.
We are able to document & list the API’s in the single collection. DIAL
This helps for our adopters as an API documentation.
But the challenge comes when an adopter wants to know what the tests that we verified or if any contributor wants to contribute some of the API’s by writing API tests in postman itself.
We can’t do all of these in single API collection. Hence we created the separate collection to write positive, negative & multiple scenarios to verify our service.
DIAL API tests
Is it the right way of adding API documentation & list of API’s in one collection, and different collection for tests?