Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Api testing guide API Testing Guide An automated approach to API testing transformation From Monolith to Microservice The consumerization of IT has changed the way we write applications today Instead of building a single monolithic system that is installe

API Testing Guide An automated approach to API testing transformation From Monolith to Microservice The consumerization of IT has changed the way we write applications today Instead of building a single monolithic system that is installed on a server in a back o ?ce or call center modern applications are scattered within mobile devices and web browsers so users can gain access to services at anytime from anywhere And modern applications are no longer self-contained they are composed of multiple service components that are tied together at runtime Therefore the end-user experience is not powered by the elegant UIs we all use but by APIs that facilitate interactions between code modules applications and back-end IT systems Because of this the way we test must change Quality assurance QA and development teams must expand their capacity to test each layer of the application as well as the end-to-end business transactions Modern applications then require comprehensive API testing in addition to traditional UI testing But API testing presents many challenges for testers It requires a new approach ??one that is automated wherever possible and inherently data- driven When testing APIs testers are faced with numerous discrete units of work Some of these APIs may have been created by a third party while the possible ordering and combinations of di ?erent versions of APIs can cause the number of combinations that need to be tested to skyrocket to an impossible number The ability to identify these combinations and then reduce them to a realistic number without compromising quality requires testers to adopt a new model-based approach and invest in automation technologies Related Reading Article from Professional Tester Magazine ?? Meeting the Challenge of API Testing The Challenges of API Testing Your inclination may be to extend the same principals of UI testing to APIs ??have developers build a UI in front of each API and put your ??eyes on the glass ? using manual testing to input spreadsheets of data and watch the response This approach however is not ideal takes too long and will not scale These challenges are exacerbated for several reasons Use case proliferation Traditional UI testing is concerned only with the functionality of the overall application A tester exercises an input and interprets the output against expected outcomes But API testing is a di ?erent animal Because APIs are the central hub of logic and the gateway to data for many applications use cases are near-limitless As a result the number of required tests quickly surpasses the capabilities of the development and technical testers responsible for test case design Asynchronous and synchronous processes Modern applications are complex and one API may link together several microservices and other APIs As a result a single call on an API may trigger any number of parallel and serial actions For example one service may look up a customer ? s shipping address while a second service looks up the price of an item A third service then takes the output to calculate