TESTERS 4.8 KB

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