Content deleted Content added
ordering links by relevance to the subject of test doubles |
m typo |
||
Line 10:
* [[Dummy object]] (used when a parameter is needed for the tested method but without actually needing to use the parameter)
For both manual and automated [[Black-box_testing|black box testing]] of [[Service-oriented_architecture|service oriented architecture]] [[Software_system|systems]] or [[Microservices|microservices]] [[Software_developer|software developers]] and [[Software_testing|testers]] use test doubles that communicate with the [[System_under_test|system under test]] over a network protocol<ref>Clemson, Toby [https://martinfowler.com/articles/microservice-testing/#testing-component-out-of-process-diagram "Testing Strategies in a Microservice Architecture"], ''martinfowler.com'', 18 November 2014. Retrieved on 07 December 2017.</ref><ref>Byars, Brandon. "Testing Microservices with Mountebank", ''[[Manning Publications]]'', MEAP began March 2017. ISBN 9781617294778. Retrieved on 07 December 2017.</ref>. These test doubles are called different names depending on the tool vendor. A commonly used term is [[Service_virtualization|service virtualization]].
<ref>Bulaty, Wojciech [https://www.infoq.com/articles/stubbing-mocking-service-virtualization-differences "Stubbing, Mocking and Service Virtualization Differences for Test and Development Teams"], ''[[InfoQ]]'', 19 February 2016. Retrieved on 07 December 2017.</ref>.
|