cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

import p5-DBD-Mock

Browse Source 
Testing with databases can be tricky.  If you are developing a system
married to a single database then you can make some assumptions about
your environment and ask the user to provide relevant connection
information.  But if you need to test a framework that uses DBI,
particularly a framework that uses different types of persistence
schemes, then it may be more useful to simply verify what the framework
is trying to do -- ensure the right SQL is generated and that the
correct parameters are bound.
DBD::Mock makes it easy to just modify your configuration (presumably
held outside your code) and just use it instead of DBD::Foo (like
DBD::Pg or DBD::mysql) in your framework.

ok sthen@
This commit is contained in:
simon 2007-11-22 19:43:34 +00:00
parent 665c4affa2
commit 120cb7a782
4 changed files with 43 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
databases/p5-DBD-Mock/Makefile Normal file
View File

@ -0,0 +1,23 @@
# $OpenBSD: Makefile,v 1.1.1.1 2007/11/22 19:43:34 simon Exp $
COMMENT= mock database driver for testing
MODULES= cpan
DISTNAME= DBD-Mock-1.36
CATEGORIES= databases devel
MAINTAINER= Simon Bertrang <simon@openbsd.org>
# Perl
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
RUN_DEPENDS= ::databases/p5-DBI
CONFIGURE_STYLE=modbuild
MAKE_ENV+= TEST_POD=1
.include <bsd.port.mk>

5
databases/p5-DBD-Mock/distinfo Normal file
View File

@ -0,0 +1,5 @@
MD5 (DBD-Mock-1.36.tar.gz) = RDFrhM7upHZcJKdcr8sZrg==
RMD160 (DBD-Mock-1.36.tar.gz) = GFNHVdod97i2djhK33VQbrs/TSE=
SHA1 (DBD-Mock-1.36.tar.gz) = 79u1ZsWXHqIMMB257UC6J/pyANQ=
SHA256 (DBD-Mock-1.36.tar.gz) = tgNO08ObYh8o2beLWtDz431TtDvCiojwwqsYxIXDCQ0=
SIZE (DBD-Mock-1.36.tar.gz) = 37835

11
databases/p5-DBD-Mock/pkg/DESCR Normal file
View File

@ -0,0 +1,11 @@
Testing with databases can be tricky. If you are developing a system
married to a single database then you can make some assumptions about
your environment and ask the user to provide relevant connection
information. But if you need to test a framework that uses DBI,
particularly a framework that uses different types of persistence
schemes, then it may be more useful to simply verify what the framework
is trying to do -- ensure the right SQL is generated and that the
correct parameters are bound.
DBD::Mock makes it easy to just modify your configuration (presumably
held outside your code) and just use it instead of DBD::Foo (like
DBD::Pg or DBD::mysql) in your framework.

4
databases/p5-DBD-Mock/pkg/PLIST Normal file
View File

@ -0,0 +1,4 @@
@comment $OpenBSD: PLIST,v 1.1.1.1 2007/11/22 19:43:34 simon Exp $
${P5SITE}/DBD/
${P5SITE}/DBD/Mock.pm
@man man/man3p/DBD::Mock.3p