What does API testing mean? -
when new api created developer , sent tester testing , how should new api tester begin testing of api?
it seem simple question after reading many articles api, confused it.
can please provide right way understand, api is, why required, need tested , how can tested?
note : purely new api , vary badly need larn api , concepts in detail
thank in advance
there multiple approaches software testing, , relationship between test , dev work can vary great deal 1 team next. similarly, how much testing given api or component deserves time/budget decision. in abstract though, regardless of sdlc process, i'd thorough api testing should cover @ to the lowest degree following:
documentation
api documentation should part of final deliverable, , should written dev rather test team. test team needs ensure documentation adequate (what "adequate" means vary intended audience), , provides sufficient info interact api.
discovery testing
the test grouping should manually exercise set of calls documented in api (eg, verifying particular resource exposed api can created, listed, updated, , deleted appropriate). can occur via commandline client (eg, curl http api), via api-wrapper library or via lightweight scripted client.
usability testing
usability testing evaluates whether api functional , friendly perspective of client (typically software developer) using build something. api integrate platforms intended for? consistent, , @ reasonable level of abstraction? basically, create sense?
security testing
are security requirements defined api? type of authentication, if any, required, , permissions structures may apply? sensitive info encrypted, sent on https, or both? there ways people can access things shouldn't?
automated testing
in general, api testing should culminate in creation of set of scripts, or tool, can used regularly exercise api , study errors minimal human interaction.
api
No comments:
Post a Comment