Please enable JavaScript.
Coggle requires JavaScript to display documents.
1. API TESTING :checkered_flag: - Coggle Diagram
1. API TESTING
:checkered_flag:
Functional testing
Functional test
to test against function requirement
Integration test
to test several API calls, E2E
to test
intra-service communications
and
data transmissions
:star:
Regression test
to ensure bug fix & new features don't break the existing behaviours of APIs
Sanity test
quick evaluation to determine whether a software product is functioning correctly after adding a new module or functionality to an existing product
After many regressions or a minor change in the code, a build is received.
After bug fixing, the build is delivered.
Before the production deployment.
UI test
to test the UI interactions with the APIs
to make sure the data can be
displayed properly
Smoke test
to validate API development, if working or not
Non-functional testing
Stress test
create high loads to the APIs
test if the APIs are able to function normally
Security test
:red_flag:
to test the APIs against all possible
external threats
Fuzz test :red_flag:
injects invalid or unexpected input data into the API
tries to crash the API
to identifies the API vulnerabilities
Load test (Performance test)
simulate different loads :star:
to calculate the
capacity
of the APPL
TOOLs
: Load Runner,
Apache Jmeter tool
, Gatling...
The key objectives of performance testing
Evaluating Response Time
Measuring Throughput
Resource Utilization
Scalability Evaluation
Detecting Bottlenecks
How to choose tools
Testing Objectives, Supported Protocols, Realistic Load Simulation, Reporting and Analysis, Integrations, Cost and Licensing