API testing: Difference between revisions

Revision as of 13:30, 25 April 2023

Revision as of 13:43, 25 April 2023

Line 33:

*[[Load test]] - This type of testing simulates real-world workloads to see how a system or application performs. The goal is to find bottlenecks and determine the maximum number of users or transactions the system can handle.

*[[Performance testing]] - This type of testing evaluates how an API performs under certain conditions to assess the API's ability to handle high loads and maintain high-performance levels. There are two main types of API performance testing: functional testing and load testing.

*[[Security testingTesting]] - This series of tests checks for vulnerabilities in APIs using various techniques. The goal is to find and fix security gaps and ensure basic security requirements are met. API scanningIt involves mimicking hacker actions to find bugs. This helpsand prevent attackers from accessing or disrupting the API or its data.

*[[Penetration testingTesting]] - ThisEthical hacking is an ethical hacking processused to assess the security of an API design. It is conducted by anAn external pentester to findfinds vulnerabilities in API integrations due to incorrect business logic or programming issues. The goal is to identify security vulnerabilities that attackers could exploit to access sensitive data or perform malicious actions.

*[https://docs.oracle.com/cd/E55956_01/doc.11123/external_user_guide/content/wsi_compliance.html WS-* compliance testing] - This testing applies to SOAP APIs and ensures proper implementation of standards such as WS-Addressing, WS-Discovery, WS-Federation, WS-Policy, WS-Security, and WS-Trust.

*[[Graphical_user_interface_testing|Web UI testing]] - Checks if the visual elements of a web application's user interface work correctly and are user-friendly. It is different from API testing, which tests the communication between software components.