API testing: Difference between revisions

Revision as of 10:04, 3 November 2016

Revision as of 13:04, 14 November 2016

Line 10:

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

API Testing is recognizedrecognised as being more suitable for [[test automation]] and [[continuous testing]] (especially the automation used with [[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 31:

==API testing tools==

[[ForresterForester Research]] identified nine tools that met their criteria for API Testing and Test Automation. All tools that met the criteria were desktop-based tools. Based on a 40-criteria evaluation, the tools were ranked in the following order:<ref name="forrblog"/>

# [[Parasoft]] [[SOAtest]] and Development Testing Platform

# [[IBM]] Rational Test Workbench

Line 37:

# [[Tricentis|Tricentis Tosca]]

# [[CA, Inc.|CA]] Application Test

# [[Hewlett-Packard|HP]] [[HP QuickTestQuick Test Professional|Unified Functional Testing]] and Business Process Testing

# [[Microsoft]] [[Visual Studio]]

# SmartBearSmart Bear Ready! API ([[SoapUI]] successor) and [[TestCompleteTest Complete]]

# [[TestPlantTest Plant]] [[Eggplant Functional]]

==See also==

* [[Automated testing]]

* [[Service virtualizationvirtualisation]]

* [[Software testing]]