As you’ve found there’s a whole raft of outdated, poor and convoluted information around unit testing in WP currently. However Josh Pollock, a well respected WordPress dev and Core contributor did a YouTube series on testing in WordPress least year which I found very helpful. As I’ve been on the unit testing in WordPress journey …
You’re on a Mac! You have two of the three components you need for a Web server by default. Apache and PHP. All you need to do now is get MySQL. There are plenty of tutorials on how to do this and can be found with Google. Of course NW Tech recommendation of MAMP is …
Unit Test ignores stubbed method second time around in a dataProvider
Integration test – remove the mu plugins in the test
In order of preference: composer require wp-phpunit/wp-phpunit –dev. Depending on the IDE you use you might need to mark the package in vendor/ as a source directory. Each IDE allows you to add definitions from external libraries. In PHPStorm it’s Settings → Languages & Frameworks → PHP → Include Path. Just copy the files over …
No. And even if there was, it would be probably useless anyway. You would get incorrect results, because a .php file might call slow functions from WordPress core files, and there are a lot of situations like this. You could try using the xdebug extension, it’s pretty close to what you’re looking for
I don’t think it is common enough task for there to be generic recommendations in WordPress area. Taking the more specific part of your question — manipulating template is certainly possible and quite common. Any template (being loaded in native fashion) will have to go through template_include filter Results of single template specifically will go …
That seems to be an old repo, you should use https://core.trac.wordpress.org/browser/trunk/tests. Obviously trunk should be used if you want to use the tests with 4.6. Not sure how much difference there is in the infrastructure between the version (in other words, it is unlikely that you care how core does a specific test, therefor the …
OK, I was reading from an outdated tutorial. Command for running tests is now: vendor/bin/phpunit <path_to_file> This command should be Run from root directory of wordpress.
It does not work because that’s not the mu-plugins folder. The mu-plugins folder goes in the wp-content folder at wp-content/mu-plugins. Note that mu-plugins is not the same as plugin folder, but rather a place that you can put arbitrary PHP files that are all loaded. Files in subfolders are not loaded, and files are not …
