README 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103
  1. SimpleTest
  2. ==========
  3. You probably got this package from:
  4. http://simpletest.org/en/download.html
  5. If there is no licence agreement with this package please download
  6. a version from the location above. You must read and accept that
  7. licence to use this software. The file is titled simply LICENSE.
  8. What is it? It's a framework for unit testing, web site testing and
  9. mock objects for PHP 5.0.5+.
  10. If you have used JUnit, you will find this PHP unit testing version very
  11. similar. Also included is a mock objects and server stubs generator.
  12. The stubs can have return values set for different arguments, can have
  13. sequences set also by arguments and can return items by reference.
  14. The mocks inherit all of this functionality and can also have
  15. expectations set, again in sequences and for different arguments.
  16. A web tester similar in concept to JWebUnit is also included. There is no
  17. JavaScript or tables support, but forms, authentication, cookies and
  18. frames are handled.
  19. You can see a release schedule at http://simpletest.org/en/overview.html
  20. which is also copied to the documentation folder with this release.
  21. A full PHPDocumenter API documentation exists at
  22. http://simpletest.org/api/.
  23. The user interface is minimal in the extreme, but a lot of information
  24. flows from the test suite. After version 1.0 we will release a better
  25. web UI, but we are leaving XUL and GTK versions to volunteers as
  26. everybody has their own opinion on a good GUI, and we don't want to
  27. discourage development by shipping one with the toolkit. You can
  28. download an Eclipse plug-in separately.
  29. The unit tests for SimpleTest itself can be run here:
  30. test/unit_tests.php
  31. And tests involving live network connections as well are here:
  32. test/all_tests.php
  33. The full tests will typically overrun the 8Mb limit often allowed
  34. to a PHP process. A workaround is to run the tests on the command
  35. with a custom php.ini file or with the switch -dmemory_limit=-1
  36. if you do not have access to your server version.
  37. The full tests read some test data from simpletest.org. If the site
  38. is down or has been modified for a later version then you will get
  39. spurious errors. A unit_tests.php failure on the other hand would be
  40. very serious. Please notify us if you find one.
  41. Even if all of the tests run please verify that your existing test suites
  42. also function as expected. The file:
  43. HELP_MY_TESTS_DONT_WORK_ANYMORE
  44. ...contains information on interface changes. It also points out
  45. deprecated interfaces, so you should read this even if all of
  46. your current tests appear to run.
  47. There is a documentation folder which contains the core reference information
  48. in English and French, although this information is fairly basic.
  49. You can find a tutorial on...
  50. http://simpletest.org/en/first_test_tutorial.html
  51. ...to get you started and this material will eventually become included
  52. with the project documentation. A French translation exists at:
  53. http://simpletest.org/fr/first_test_tutorial.html
  54. If you download and use, and possibly even extend this tool, please let us
  55. know. Any feedback, even bad, is always welcome and we will work to get
  56. your suggestions into the next release. Ideally please send your
  57. comments to:
  58. simpletest-support@lists.sourceforge.net
  59. ...so that others can read them too. We usually try to respond within 48
  60. hours.
  61. There is no change log except at Sourceforge. You can visit the
  62. release notes to see the completed TODO list after each cycle and also the
  63. status of any bugs, but if the bug is recent then it will be fixed in SVN only.
  64. The SVN check-ins always have all the tests passing and so SVN snapshots should
  65. be pretty usable, although the code may not look so good internally.
  66. Oh, and one last thing: SimpleTest is called "Simple" because it should
  67. be simple to use. We intend to add a complete set of tools for a test
  68. first and "test as you code" type of development. "Simple" does not mean
  69. "Lite" in this context.
  70. Thanks to everyone who has sent comments and offered suggestions. They
  71. really are invaluable, but sadly you are too many to mention in full.
  72. Thanks to all on the advanced PHP forum on SitePoint, especially Harry
  73. Fuecks. Early adopters are always an inspiration.
  74. -- Marcus Baker, Jason Sweat, Travis Swicegood, Perrick Penet and Edward Z. Yang.