Differences

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

--- qa:runtests:documentation [2009/09/01 19:13] – zoe
+++ qa:runtests:documentation [2009/09/01 19:45] – zoe
@@ Line 3: / Line 3: @@
   *[[http://wiki.php.net/qa/runtests/documentation/commandline|Command line options]]
-A list of the options available in the hold version of run-tests and information about whether that are (or will be) re-implemented.
+A list of the options available in the old version of run-tests and information about whether that are (or will be) re-implemented.
 ====== Introduction ======
-runtests is a test environment written in PHP. It is used to tests PHP itself.
+runtests is a test environment written in PHP. It is used to test PHP itself.
 It is not a replacement for unit test frameworks like PHPUnit.
 The basic principle of automated tests is very simple. Compare a computed
 result with some pre-calculated "known good", expected value.
-If both match, the test has passed. If they do not match, the tests failes, and
+If both match, the test has passed. If they do not match, the tests fails, and
 there is probably a bug in PHP, or some precondition for the test was not met.
 Testing PHP is a far more complex issue than it may seem at first glance,
 because each test may require an individual PHP configuration, certain settings
-at operting system level (for example environment variables), or even external
+at operating system level (for example environment variables), or even external
 services (like databases, LDAP servers or IMAP servers).
@@ Line 54: / Line 54: @@
 We have already mentioned that tests need an individual environment. Not all
-tests can be run at the command line, for example. If a test need to make
+tests can be run at the command line, for example. If a test needs to make
 sure that PHP returns correct HTTP header, or processes GET or POST input,
 the test probably requires the CGI SAPI to run.
+The implementation of runtests that is described in these pages is specific to PHP5.3 and beyond. Many of the implementation details are similar to the previous version of runtests but the overall code structure is very different.
+====== Overall code structure ======
+The most important classes in classes in the code are shown in the figure below and described in the following paragraphs.
+{{:qa:runtests:mainclasses.png|}}
+===== Test Run =====
+The main class is rtPhpTestRun. This class is responsible for the overall running of one or more test cases.
+rtPhpTestRun instantiates the run configuration class (rtRuntestsConfiguration, see Configuration) and then executes a single test or a group of tests.
+===== Test Group =====
+A test group (rtPhpTestGroup) is currently defined as all of the tests within a single directory.  It seems likely that groups of tests can be run in parallel, teh prototype code is designed to enable that.
+There is currently no group configuration class, however, it is possible that one may be required. For example there might be groups of tests that cannot be run at the same time as other groups (tests with REDIRECT?).
+===== Test Case =====
+Each test case is executed in it's own process. Many classes are associated with the execution of a single test case. The following subsections give a brief description of the responsibilities of each class.
+====== Configuration classes ======
 ====== Parallel Execution ======

Differences

Page Tools