aboutsummaryrefslogtreecommitdiff
path: root/devel/p5-Mock-MonkeyPatch/pkg-descr
diff options
context:
space:
mode:
Diffstat (limited to 'devel/p5-Mock-MonkeyPatch/pkg-descr')
-rw-r--r--devel/p5-Mock-MonkeyPatch/pkg-descr10
1 files changed, 10 insertions, 0 deletions
diff --git a/devel/p5-Mock-MonkeyPatch/pkg-descr b/devel/p5-Mock-MonkeyPatch/pkg-descr
new file mode 100644
index 000000000000..e0d8541199c5
--- /dev/null
+++ b/devel/p5-Mock-MonkeyPatch/pkg-descr
@@ -0,0 +1,10 @@
+Mocking is a common tool, especially for testing. By strategically
+replacing a subroutine, one can isolate segments (units) of code to
+test individually. When this is done it is important to know that the
+mocked sub was actually called and with what arguments it was called.
+
+Mock::MonkeyPatch injects a subroutine in the place of an existing one.
+It returns an object by which you can revisit the manner in which the
+mocked subroutine was called. Further when the object goes out of scope
+(or when the "restore" method is called) the original subroutine is
+replaced.