Let me start by saying that the init action is called when WordPress is loaded, before the tests are run. So it you are having your plugin/theme loaded with WordPress (by hooking into muplugins_loaded, for example), the register_my_type() method should be getting called, if your constructor is being called before init. (If you aren’t loading … Read more
I think the main problem here is that you are loading WordPress’s bootstrap too early. Changing to this should fix it (I’ve interspersed comments explaining why things are in the order they are in): // This file contains tests_add_filter(), so we need to load it // so that we can hook the _manually_load_plugin() function to … Read more
As the testing database is (usually, and should be) a separate database, you will need to set the appropriate option value in the setUp routine (using add_option or update_option). I would also recommend deleting or reseting the option in the teardown method as well, but I have had issues when trying to drop tables (see … Read more
The unit tests transform all CREATE TABLE and DROP TABLE queries to CREATE TEMPORARY TABLE and DROP TEMPORARY TALBE, respectively. So in your tearDown the query will attempt to drop temporary tables with those names, but not the actual tables. To fix this, add this before your DROP queries: remove_filter( ‘query’, array( $this, ‘_drop_temporary_tables’ ) … Read more
tl;dr: is there a way to make changes to WordPress options during a PHPUnit test suite execution, and have the changes reverted to the WordPress defaults before the next test suite is executed, without writing a custom teardown function? Yes, and no. No, you cannot use the code you currently have and expect this result. … Read more
Travis is a hosted continuous integration service. Travis takes the files you’ve committed to your Github repo, and runs PHPUnit against them. Notably different than running phpunit in your local environment is that running tests on Travis requires at least three steps: Commit to Git. Push to Github. Wait for Travis to create and run … Read more
If you use wp_die() you can utilize the tools included with WordPress’s PHPUnit test suite. The WP_Ajax_UnitTestCase provides the _handleAjax() method that will hook into the actions called by wp_die() and throw an exception, which will prevent die() from being called. I’ve written a tutorial on how to use WP_Ajax_UnitTestCase, which explains all of the … Read more
What is the best way to do unit tests for your plugin in 2018 [closed]
This class is defined in includes/testcase.php. If you checkout the entire repo, you should have it. To check out the entire repo, you should be running something along the lines of: svn co https://unit-tests.svn.wordpress.org/trunk wordpress-tests
I have a setup similar to yours, with MAMP. I also have had this problem with PHPUnit. It seems that no matter what you do, PHPUnit does not recognize the include_path from MAMP. You have to add the correct path to the php.ini in /private/etc/.