On 02.05.13 21:26, Jens Rehsack wrote:
Hi all,I got a bit lost in to much complexity of doing the whole world at once ... For now I committed a compiling version without really much functionality (but for reviewing ...) and plan to do following things at next: * ignore anything of configurable stuff (like DBI::PurePurl, Gofer-Proxy) * simply generate t/@dirs/${test}.t from the names from DBI::Test::(NameSpaces::)List->test_cases * see what "works" from the things are in lib/DBI/Test/Cases/*.pm and add it to test_cases sub Then we shall decide how to go on. My suggestion is: 1) build an "internal" version and re-build DBI's DBI::DBD::dbd_edit_mm_attribs() on it and slowly introduce combine_nk() and map_test_variants ... ==> do the same for SQL::Statement ==> when both internal versions of DBI and S::S work in general (without new functionality), release DBI::Test 2) Catch BooK to find synergy effects with Test::Database (DSN config, ...) Another way to go on is release soon without much functionality but reserving the name space. If anyone has more suggestions, enhancements etc. - please share them ;) Cheers
I think there is now a good state committed in perl5-dbi/DBI-Test I used $ perl Makefile.PL $ env DBI_MOCK=1 make test # runs tests with DBI::Mock $ make test # runs tests with DBI (when installed) Now it's on Ribasushi, Joakim Tørmoen and Vince Willems to improve the test cases itself. Cheers -- Jens Rehsack
