| Name : perl-DBD-Mock
| |
| Version : 1.59
| Vendor : obs://build_opensuse_org/devel:languages:perl
|
| Release : lp154.1.1
| Date : 2023-01-27 16:19:59
|
| Group : Unspecified
| Source RPM : perl-DBD-Mock-1.59-lp154.1.1.src.rpm
|
| Size : 0.19 MB
| |
| Packager : https://www_suse_com/
| |
| Summary : Mock database driver for testing
|
Description :
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.
There is no distinct area where using this module makes sense. (Some people
may successfully argue that this is a solution looking for a problem...)
Indeed, if you can assume your users have something like DBD::AnyData or
DBD::SQLite or if you do not mind creating a dependency on them then it
makes far more sense to use these legitimate driver implementations and
test your application in the real world -- at least as much of the real
world as you can create in your tests...
And if your database handle exists as a package variable or something else
easily replaced at test-time then it may make more sense to use
Test::MockObject to create a fully dynamic handle. There is an excellent
article by chromatic about using Test::MockObject in this and other ways,
strongly recommended. (See SEE ALSO for a link)
|
RPM found in directory: /packages/linux-pbone/ftp5.gwdg.de/pub/opensuse/repositories/devel:/languages:/perl:/CPAN-D/15.4/noarch |
