Requirements DSN::Provider / Test::Database

Hi,

the discussion whether to re-use Test::Database or develop a probably
common ancestor should base on goals, scope and requirements as it
seems to be reasonable for DBIT …

  Goals: ("how will we know if this project is or is not a success")

    G1: Out of the box any DBIT Test Case can be run against any
        (suitable) driver tunable configuration.

    G2: Supports beside DBI/DBD tests also applications and DBIC

  Scope: (the boundaries and deliverables of the project)

    S1: CREATE TABLE necessary?

    S2: DBI::Mock ?

  Requirements:

    R1: Must not require DBI (for being useful for SQL::Statement)

    R2: Must be able to distinguish between simple tests (where
        driver defaults are fine) and exhaustive tests (all tunable's
        shall be tested)

    R3: Must be able to use environment settings for detailed
        connection target information

    R4: Must be able to rely on configuration for non-DBI/DBD test
        cases (Applications, DBIC, …)

        R4a: Must be able to determine / filter / reduce configuration
             upon tests are running
             ==> for DBD::xyz (don't deliver DBD::abc DSN's)
             ==> for applications (deliver the DSN's for the DBD's
                 the application is using)
             ==> for DBIC and alike (deliver all configured DSN's)

Best regards
-- 
Jens Rehsack
[email protected]