Differences

This shows you the differences between two versions of the page.

--- 2015:mock_objects_in_functional_testing [2014/11/06 02:01] – created jonjagger
+++ 2015:mock_objects_in_functional_testing [2016/06/11 14:05] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 \\
 **Title**: Mock objects in functional testing\\
-**Proposer**: [[2015:Svwn Rosvall]]\\
+**Proposer**: [[2015:Sven Rosvall]]\\
 **Type**: Tutorial and case-study\\
 **Duration**: 90 mins\\
 **Description**: \\
-Mock objects are great. They simplify testing enormously and are crucial for unit testing. There are many mocking frameworks available for many languages. But most of them are designed only for unit testing. Don’t you wish you could use them in functional testing where the system under test, instead of being controlled from the test code, executes in its production-like environment and interacts with other systems in other processes or other servers? You want to test that the configuration for your service/program/whatever-you-call-it is correct and actually communicates via network, message queues etc. \\
+Mock objects are great. They simplify testing enormously and are crucial for unit testing. There are many mocking frameworks available for many languages. But most of them are designed only for unit testing. Don't you wish you could use them in functional testing where the system under test, instead of being controlled from the test code, executes in its production-like environment and interacts with other systems in other processes or other servers? You want to test that the configuration for your service/program/whatever-you-call-it is correct and actually communicates via network, message queues etc. \\
 \\
 This talk describes how to use some tools available and methods for creating your own framework for letting your system under test communicate with endpoints that mimic an external system that is accessed through different inter-process methods.\\