Title: [Plugin: wp-unit] Poor documentation
Last modified: August 20, 2016

---

# [Plugin: wp-unit] Poor documentation

 *  [cristiroma](https://wordpress.org/support/users/cristiroma/)
 * (@cristiroma)
 * [14 years, 3 months ago](https://wordpress.org/support/topic/plugin-wp-unit-poor-documentation/)
 * When I wrote a test
 * `class MyTest extends PHPUnit_Framework_TestCase {`
 * I get
 * `Fatal error: Class 'PHPUnit_Framework_TestCase' not found in /home/test/workspace/
   myproject/www/wp-content/plugins/myth/tests/tests.php on line 33`
 * Is there any documentation on how to actually implement these tests? Do I need
   to use require_once?
    Is there a problem with plugins loaded in wrong order?
 * [http://wordpress.org/extend/plugins/wp-unit/](http://wordpress.org/extend/plugins/wp-unit/)

Viewing 1 replies (of 1 total)

 *  Plugin Contributor [nunomorgadinho](https://wordpress.org/support/users/nunomorgadinho/)
 * (@nunomorgadinho)
 * [14 years ago](https://wordpress.org/support/topic/plugin-wp-unit-poor-documentation/#post-2548492)
 * Every unit test must be included in the ‘testcase’ folder you will find under
   the wp-unit plugin directory. Also you’ll find a couple of examples there to 
   help you get started.

Viewing 1 replies (of 1 total)

The topic ‘[Plugin: wp-unit] Poor documentation’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-unit.svg)
 * [wp-unit](https://wordpress.org/plugins/wp-unit/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-unit/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-unit/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-unit/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-unit/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-unit/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [nunomorgadinho](https://wordpress.org/support/users/nunomorgadinho/)
 * Last activity: [14 years ago](https://wordpress.org/support/topic/plugin-wp-unit-poor-documentation/#post-2548492)
 * Status: not resolved