[Sommaire] [Imprimer]

   1  ===================
   2  HOW TO TEST PEAR DB
   3  ===================
   4  
   5  $Id: TESTERS,v 1.19 2004/04/30 02:45:16 danielc Exp $
   6  
   7  
   8  INTRODUCTION
   9  ============
  10  
  11  These are instructions for testing PEAR DB on a Windows machine using a
  12  Cygwin Bash shell.  Adjust the paths and commands to match your system.
  13  This configuration is used because these precise steps are known to work.
  14  
  15  NOTE:  You must log on as a user which has permissions to modify the
  16  contents of your PHP executable's directory.  This is necessary for both
  17  configuring AND running the test system.
  18  
  19  
  20  INSTALLATION
  21  ============
  22  
  23  Obtain PHP's Test Framework
  24  ---------------------------
  25  If you don't have PHP's test framework, you need to obtain it.  These
  26  steps include changing the working directory, downloading run-tests.php
  27  via CVS and copying the file into place.  Change the revision flag in the
  28  CVS command as appropriate for your present version of PHP.
  29  
  30   cd c:/progra~1/php
  31   cvs -d :pserver:cvsread@cvs.php.net:/repository login   # password is phpfi
  32   cvs -d :pserver:cvsread@cvs.php.net:/repository co -r PHP_4_3 \
  33       -d test php-src/run-tests.php
  34   cp test/run-tests.php .
  35   rm -rf test
  36  
  37  
  38  Obtain DB and its Test Framework
  39  --------------------------------
  40  * IF PEAR DB IS ALREADY INSTALLED:
  41  
  42    If you have PEAR DB installed already, good.  The test suite
  43    is in place.  Open up a command/shell prompt and move into
  44    the test directory.
  45  
  46     cd <path to pear insall>/tests/DB/tests
  47  
  48  * VIA A NEW INSTALLATION USING THE PEAR INSTALLER:
  49  
  50    Installing PEAR has gotten fairly easy.  Follow the instructions
  51    from the manual:  http://pear.php.net/manual/en/installation.php
  52    Once PEAR and DB are installed, move to the test directory.
  53  
  54     cd pear/tests/DB/tests
  55  
  56  * VIA CVS:
  57  
  58    Create a location to store the test installation of DB and its
  59    test scripts.
  60  
  61     mkdir d:/peartest
  62     cd d:/peartest
  63     cvs -d :pserver:cvsread@cvs.php.net:/repository co -P pear/DB
  64  
  65    We assume you already have the PEAR base package installed.  If
  66    you don't, you will need to do so, but the instructions for
  67    doing that are beyond the scope of this document.  See
  68    http://pear.php.net/manual/en/installation.php for more info.
  69  
  70    Move to the test directory.
  71  
  72     cd pear/DB/tests
  73  
  74  
  75  Copy the Starter Shell Script and Edit the Paths
  76  ------------------------------------------------
  77  To make starting up each test run easier, we have included two shell
  78  scripts.  The original files are named "run.cvs".  They need to be
  79  renamed to "run" so CVS won't bother you with tracking them.  Then,
  80  the paths and file names in them need to be set to those used by
  81  your system.
  82  
  83   cp run.cvs run
  84   chmod 755 run
  85   vi run
  86  
  87   cd driver
  88   cp run.cvs run
  89   chmod 755 run
  90   vi run
  91  
  92  
  93  Copy the Setup File and Edit the DSN's
  94  --------------------------------------
  95  The test suite contains a file that stores the DSN's needed to
  96  connect to your database.  The original file is "setup.inc.cvs"
  97  and it needs to be renamed "setup.inc" so CVS won't track it.
  98  Then you'll need to edit the DSN's in it.
  99  
 100   cp setup.inc.cvs setup.inc
 101   vi setup.inc
 102  
 103  
 104  RUN THE TESTS
 105  =============
 106  
 107  To run all tests:  ./run
 108  To run one test:   ./run <test file name>
 109  Example:           ./run db_parsedsn.phpt
 110  
 111  
 112  Test Types and Locations
 113  ------------------------
 114  tests             Common PEAR DB tests
 115  tests/driver      Common tests for all the drivers
 116  
 117  
 118  Results and What To Do With Them
 119  --------------------------------
 120  Each test that fails generates a .php (which you can execute), a .exp
 121  (the expected output), a .out (the test output) and a .diff (a diff -u
 122  from the .exp and .out files).
 123  
 124  If you run the tests, please report or fill the TEST CONFORMANCE table
 125  in the STATUS document.  Before any commit to CVS be sure to run the
 126  tests and nothing got broken with the change.
 127  
 128  If you get the message "SKIP", means that the test it's not executed.
 129  Look at the DB/tests/driver/skipif.inc to see what's the problem
 130  (probably a connection problem).
 131  
 132  
 133  DB TESTER MATRIX
 134  ================
 135                                  fbsql    ifx    mssql   mysqli   odbc   sqlite
 136  TESTER                      dbase | ibase |  msql | mysql |  oci8 | pgsql | sybase
 137  John Horton                   -   -   -   X   -   -   -   -   -   -   -   -   -
 138  Tim Zickus                    -   -   -   -   -   -   -   -   X   -   -   -   -
 139  Tim Parkin                    -   -   -   -   -   -   -   -   X   -   -   -   -
 140  Paul Gardiner                 -   -   -   X   -   -   -   -   -   -   -   -   -
 141  peterwb@iafrica.com           -   -   -   X   -   -   -   -   -   -   -   -   -
 142  Daniel, Adam                  -   -   -   -   -   -   -   -   X   -   -   -   -
 143  szii@sziisoft.com             -   -   -   -   -   -   -   -   -   X¹  -   -   -
 144  jmh3@linuxfreak.com           -   -   -   -   -   -   -   -   -   -   X   -   -
 145  Kevin Henrikson               -   -   -   -   -   -   -   -   X   -   -   -   -
 146  Stig Bakken                   -   -   -   -   -   -   X   -   -   -   X   -   -
 147  Chuck Hagenbuch               -   -   -   -   -   X   -   -   -   -   -   -   -
 148  Ludovico Magnocavallo         -   -   X   -   -   -   -   -   -   -   -   -   -
 149  Daniel Convissor              -   -   X   -   -   X   X   X   X   X²  X   X   X
 150  
 151  MISSING TESTERS               -   X   -   -   X   -   -   -   -   -   -   -   -
 152  
 153  Comments:
 154  
 155  [1]: ODBC using IBM DB2
 156  [2]: ODBC using IBM DB2 and MS Access