API testing: Difference between revisions

Revision as of 11:22, 6 January 2025

Latest revision as of 10:01, 14 February 2025

(3 intermediate revisions by 2 users not shown)

Line 11:

==API testing, GUI testing, and test automation==

API Testing is recognised as being more suitable for [[Automated_testing|test automation]] and [[Continuous_testing|continuous testing]] (especially the automation used with [[Agile_software_development|Agile software development]] and [[DevOps]]) than GUI testing.<ref name="forrblog"/><ref name="layers"/> Reasons cited include:

* '''System complexity:''' GUI tests can't sufficiently verify functional paths and back-end APIs/services associated with multitier architectures. APIs are considered the most stable interface to the system under test.

Line 21:

There are several types of tests that can be performed on APIs. Some of these include smoke testing, functional testing, security testing, penetration testing, and validation testing.

* [[Artificial intelligence]] (AI) used in API testing improves the efficiency and accuracy of the testing process. It can automatically generate test cases, identify potential issues, and analyze test results through machine learning to identify patterns and anomalies.<ref>{{cite book |last1=J. Gao, C. Tao, D. Jie ĺ, S. Lu |title=What is AI Software Testing? and Why |date=2019 |pages=27–2709 |publisher=IEEE |doi=10.1109/SOSE.2019.00015 |url=https://ieeexplore.ieee.org/document/8705808/authors#authors}}</ref>

*

*[[Smoke testing (software)|Smoke test]] - This is a preliminary test that checks if the most crucial functions of an API are working correctly and identifies any major issues before further testing.

Line 61:

|[[Katalon Studio]]

|Katalon

|-

|vStellar

|vStellar

|-

|-

|Step CI