source: trunk/server/www/vendors/simpletest/README @ 6

Last change on this file since 6 was 6, checked in by sander, 12 years ago

Added SimpleTest? test framework

File size: 4.5 KB
3You probably got this package from...
6If there is no licence agreement with this package please download
7a version from the location above. You must read and accept that
8licence to use this software. The file is titled simply LICENSE.
10What is it? It's a framework for unit testing, web site testing and
11mock objects for PHP 4.2.0+ (and PHP 5.0 to 5.3 without E_STRICT).
13If you have used JUnit, you will find this PHP unit testing version very
14similar. Also included is a mock objects and server stubs generator.
15The stubs can have return values set for different arguments, can have
16sequences set also by arguments and can return items by reference.
17The mocks inherit all of this functionality and can also have
18expectations set, again in sequences and for different arguments.
20A web tester similar in concept to JWebUnit is also included. There is no
21JavaScript or tables support, but forms, authentication, cookies and
22frames are handled.
24You can see a release schedule at
25which is also copied to the documentation folder with this release.
26A full PHPDocumenter API documentation exists at
29The user interface is minimal
30in the extreme, but a lot of information flows from the test suite.
31After version 1.0 we will release a better web UI, but we are leaving XUL
32and GTk versions to volunteers as everybody has their own opinion
33on a good GUI, and we don't want to discourage development by shipping
34one with the toolkit. YOucan download an Eclipse plug-in separately.
36You are looking at a second full release. The unit tests for SimpleTest
37itself can be run here...
41And tests involving live network connections as well are here...
45The full tests will typically overrun the 8Mb limit often allowed
46to a PHP process. A workaround is to run the tests on the command
47with a custom php.ini file if you do not have access to your server
50You will have to edit the all_tests.php file if you are accesssing
51the internet through a proxy server. See the comments in all_tests.php
52for instructions.
54The full tests read some test data from the LastCraft site. If the site
55is down or has been modified for a later version then you will get
56spurious errors. A unit_tests.php failure on the other hand would be
57very serious. As far as we know we haven't yet managed to check in any
58unit test failures, so please correct us if you find one.
60Even if all of the tests run please verify that your existing test suites
61also function as expected. If they don't see the file...
65This contains information on interface changes. It also points out
66deprecated interfaces, so you should read this even if all of
67your current tests appear to run.
69There is a documentation folder which contains the core reference information
70in English and French, although this information is fairly basic.
71You can find a tutorial on...
74 get you started and this material will eventually become included
76with the project documentation. A French translation exists at...
80If you download and use, and possibly even extend this tool, please let us
81know. Any feedback, even bad, is always welcome and we will work to get
82your suggestions into the next release. Ideally please send your
83comments to...
86 that others can read them too. We usually try to respond within 48
90There is no change log except at Sourceforge. You can visit the
91release notes to see the completed TODO list after each cycle and also the
92status of any bugs, but if the bug is recent then it will be fixed in SVN only.
93The SVN check-ins always have all the tests passing and so SVN snapshots should
94be pretty usable, although the code may not look so good internally.
96Oh, yes. It is called "Simple" because it should be simple to
97use. We intend to add a complete set of tools for a test first
98and "test as you code" type of development. "Simple" does not
99mean "Lite" in this context.
101Thanks to everyone who has sent comments and offered suggestions. They
102really are invaluable, but sadly you are too many to mention in full.
103Thanks to all on the advanced PHP forum on SitePoint, especially Harry
104Feucks. Early adopters are always an inspiration.
106Marcus Baker, Jason Sweat, Travis Swicegood, Perrick Penet and Edward Z. Yang.
Note: See TracBrowser for help on using the repository browser.