IABSD.fr/ports/databases/p5-DBD-Mock
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
cfbb239b | 2016-03-20 19:56:05 | Remove SHARED_ONLY from all CPAN Perl ports and the cpan and perl MODULES. Add WANTLIB+=perl and PKG_ARCH=* as appropriate. | |
 |
a89a097d | 2014-12-22 14:07:36 | Update to p5-DBD-Mock-1.45. remove maintainer, ok ajacoutot@ | |
|
2b8930a2 | 2014-04-13 01:01:38 | Drop USE_GROFF since groff and mandoc produce identical output. | |
 |
3f680606 | 2013-03-11 02:52:04 | PERMIT_* / REGRESS->TEST sweep | |
 |
34ea15e9 | 2011-06-13 16:40:20 | - update to 1.39 from wen heping | |
 |
aaa18858 | 2010-12-03 11:44:22 | Bump after recent cpan.port.mk change. ok jasper@ | |
|
2314c85f | 2010-11-15 00:22:45 | convert to new style depends zap default spec that are not needed convert libspecs as well convert p* to REVISION. No package changes | |
|
880de1aa | 2010-10-18 17:06:05 | USE_GROFF=Yes | |
 |
a27eb82e | 2008-07-27 22:42:41 | update to version 1.37 | |
|
120cb7a7 | 2007-11-22 19:43:34 | import p5-DBD-Mock 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@ |