Content deleted Content added
→API testing: Added hyperlink for "single-responsibility principle". |
|||
Line 24:
{{Main|API testing}}
[[API testing]] is also being widely used by software testers as it enables them to verify requirements independent of their GUI implementation, commonly to test them earlier in development, and to make sure the test itself adheres to clean code principles, especially the [[single responsibility principle]]. It involves directly testing [[API]]s as part of [[integration testing]], to determine if they meet expectations for functionality, reliability, performance, and security.<ref name="reichart1">[http://searchsoftwarequality.techtarget.com/tip/Testing-APIs-protects-applications-and-reputations Testing APIs protects applications and reputations], by Amy Reichert, SearchSoftwareQuality March 2015</ref> Since APIs lack a [[Graphical user interface|GUI]], API testing is performed at the [[Communications protocol#Layering|message layer]].<ref name="stickyminds">[http://www.stickyminds.com/interview/all-about-api-testing-interview-jonathan-cooper All About API Testing: An Interview with Jonathan Cooper], by Cameron Philipp-Edmonds, Stickyminds August 19, 2014</ref> API testing is considered critical when an API serves as the primary interface to [[application logic]].<ref>[https://www.gartner.com/en/documents/2645817 Produce Better Software by Using a Layered Testing Strategy]{{cbignore|bot=medic}}, by Sean Kenefick, [[Gartner]] January 7, 2014</ref>
===Graphical user interface (GUI) testing ===
| |||