[Bug 257466] [New port] devel/p5-Mock-MonkeyPatch ver 1.02
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257466] [New port] devel/p5-Mock-MonkeyPatch ver 1.02"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257466] [New port] devel/p5-Mock-MonkeyPatch ver 1.02: Monkey patching with test mocking in mind"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 257466] [New port] devel/p5-Mock-MonkeyPatch ver 1.02: Monkey patching with test mocking in mind"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 28 Jul 2021 02:00:28 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=257466
Bug ID: 257466
Summary: [New port] devel/p5-Mock-MonkeyPatch ver 1.02
Product: Ports & Packages
Version: Latest
Hardware: Any
URL: https://metacpan.org/dist/Mock-MonkeyPatch
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs@FreeBSD.org
Reporter: svysh.fbsd@gmail.com
Created attachment 226749
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=226749&action=edit
"git diff" for new port
Monkey patching with test mocking in mind.
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.
WWW: https://metacpan.org/dist/Mock-MonkeyPatch
- This port is needed as a new dependency for existing port
devel/p5-Workflow
- "portlint -ACN" is happy.
- "portclippy Makefile" is happy.
- Tested with:
13.0-RELEASE-p3
pkg 1.16.3
poudriere 3.3.6
perl 5.32.1
openssl 1.1.1k
ssl=base
- built-in perl tests in a clean poudriere jail say: PASS.
--
You are receiving this mail because:
You are the assignee for the bug.