view release on metacpan or  search on metacpan

README.md  view on Meta::CPAN

# DBI::Test - The DBI/DBD API Test Suite

[![Build Status](https://travis-ci.org/perl5-dbi/DBI-Test.png?branch=master)](https://travis-ci.org/perl5-dbi/DBI-Test)

## Description

This module aims at a transparent test suite for the DBI API
to be used from both sides of the API (DBI and DBD) to check
if the provided functionality is working and complete.

## Copying

Copyright (C) 2013 - The DBI development team

You may distribute this module under the terms of either the GNU
General Public License or the Artistic License, as specified in
the Perl README file.

Recent changes can be (re)viewed in the public GIT repository at
GitHub https://github.com/perl5-dbi/DBI-Test
Feel free to fork and/or clone your own copy:

   $ git clone https://github.com/perl5-dbi/DBI-Test.git DBI-Test

## Contributing

We share our thoughts on the following public channels:

1. DBI development mailing list - http://lists.perl.org/list/dbi-dev.html

2. IRC: irc.perl.org/6667 #dbi

## Build/Installation

Though this module should validate against itself, its use is
only visible when used as subset of the testsuite for DBI or a
DBD.

## Authors

This module is a team-effort. The current team members are

* H.Merijn Brand  (Tux)
* Jens Rehsack    (Sno)
* Peter Rabbitson (ribasushi)
* Joakim Tørmoen  (trmjoa)

## Some background and plans

Several of use DBI/DBD developers were playing with an idea for a long
time to come to a new way of testing DBI and DBD and especially the API
as defined by the DBI.

We have noticed in several occasions that the DBI defines the API,
where testing the API is hard because there is not (yet) an actual
database on the backend (no functional DBD) and from the other side
(the DBD) some of these tests are quite the same, just to test if the
API as documented from the DBI is working as expected from the DBD
point of view.

The plan has grown to create a new module that would replace the API
tests in the DBI test suite and that can also be used without
modification in the DBD test suites.

This way we can assure that all documented API is tested the same way
from both sides. As a bonus, we can have the DBD check that ALL DBI
functionality is implemented (or documented not to be) and that all