Differences

This shows you the differences between two versions of the page.

--- qa:runtests [2009/07/19 10:06]
zoe
+++ qa:runtests [2012/05/18 17:55]
zoe Add a page for development
@@ Line 1: / Line 1: @@
-====== Requirements ======
+====== Development pages for the new version of run-tests.php  ======
-The initial requirements for the project are described[[http://wiki.php.net/qa/runtests/requirements|here]]. Other requirements will be added as list items here with detailed descriptions (where necessary) added to the requirements documentation.
+These are the development pages for the new version of run-tests.php, the code which runs .phpt tests.
-  * Be able to skip whole directories with one check
+  * [[http://wiki.php.net/qa/runtests/requirements|Requirements]]
-  * Provide the same functionality as REDEIRECTTEST, not necessarily using the current design
+Initial requirements are listed here, additional ones will be added as we find them.
-  * Provide an API so thatthe code can be used n=by other applications (from Greg Beaver).
+  * [[http://wiki.php.net/qa/runtests/development|Development]]
+  * [[http://wiki.php.net/qa/runtests/documentation|Documentation]]
+This is developer documentation, it contains information for people who work on and maintain the code
+  * [[http://wiki.php.net/qa/runtests/howtorun|How to run the code]]
+This is for users, there are instructions for checking out runnning and testing.
+  * [[http://wiki.php.net/qa/runtests/todos|To do lists]]
+This is our current list of development items and the name of the person responsible for each one
+  * [[http://wiki.php.net/qa/runtests/decisions|Decisions]]
+Sometimes we have made a decision not to re-implement a feature of run-tests or to do something differently. The reasons for making such decions are recorded here.
+  * [[http://wiki.php.net/qa/runtests/QA|QA status]]
+Compatibility with the old version and checking that the parallel code gives the same results as sequential code are both important. The most recent state of testing is given here.
+  * [[http://wiki.php.net/qa/runtests/faq|FAQs]]
-More documentation and source code can be found here [[http://cvs.php.net/viewvc.cgi/phpruntests/documentation/|here]].
-====== ToDo & who ======
-  * Add a check for 5.3 only (Georg - done, 6th may)
-  * Implement valgrind (high priority from Nuno)
-  * Implement CGI tests (Zoe)
-    * GET (done, 27 April)
-    * POST (done 28th April)
-    * POST_RAW (done 3rd May)
-    * GZIP_POST (done 28th April)
-    * DEFLATE_POST (done 28th April)
-    * EXPECTHEADERS (done May)
-    * COOKIE (done 3rd May)
-  * Implement FILE_EXTERNAL (Georg, done)
-  * Prototype parallel running (Georg - first prototype committed)
-  * Replace the test status array with a status object (Zoe - done, 8th June)
-===== TODOs 30th June =====
-  * Run sequential groups within in Georg's schedulers (G - Done)
-  * Write whole object to disk (check timing differences, if none leave as it, otherwise Win/Lin versions) (G - Done)
-  * Refactor output writer - and task test group and task receiver. (G - Done)
-  * Focus more on QA
-     * Assemble a set of standard tests (Z - Done, see QA/QATESTS.tgz + README)
-     * Checkin results for running them with old version and current version of our code (Z, done. See LinuxQAJuly18)
-     * Write phing task to compare them (S)
-     * Always run Unit tests before checkin (All)
-     * Add new unit test whenever we find a problem (All)
-     * Always check output for notices and warnings (All)
-  * Always do clean checkout, never use cvs up (All)
-  * Use rtException everywhere, get rid of other exception classes (Z)
-====== Record of development decisions ======
-  * Use the [[http://pear.php.net/manual/en/standards.php|PEAR coding standard]] (22/04/2009 - see php-qa list for concerns)
-  * Deviation from the standard: Do not use _ prefix for private members. (Reason: too much re-work to existing code)
-  * We prefix classnames with rt (Reason: avoid name conflicts with built-in PHP classes)
-  * We do not follow the original PEAR class naming scheme   (Reason: we use autoload and name prefixes, so we can keep classnames shorter than DIR_DIR_DIR_CLASS)
-  * We will not include both File and Class doc blocks. (Reason: Only ever one class per file)
-This page [[wiki.php.net/qa/runtests/configuration]] (the address is a bit screwy, but I won't change it as I've posted a link to it) has a list of currently implemented options, and whether we will re-implement or not. Yes means we will - blank means not decided, have asked for input on QA list.
-==== Additional Options ====
-  * Run tests in parallel?
-  * XML or CSV or TXT (to replace HTML)
-  * Option specify arguments to valgrind
-====== Things that will not be re-implemented ======
-This section is here to record differences between the new and old implementation of run-tests where they affect the excecution of existing tests or the manner in which run-tests.php is executed.
-===== GZIP_POST, DEFLATE_POST =====
-The way these are currently implemented the test has to look like this:
-<code>
---POST--
-Some posted content
---GZIP_POST--
---FILE--
-etc
-</code>
-This isn't really necessary. In the new implementation the --GZIP_POST-- section will just contain the content to be posted and gzip'd. Same for DEFLATE_POST.
-This affects two tests:
-  * ext/soap/tests/server019.phpt
-  * ext/soap/tests/server020.phpt
-====== Subpages ======
-  * [[/qa/runtests/configure|configure-options]]
-  * [[/qa/runtests/runningtests|runningtests]]

Differences

Page Tools