April 13, 2017
If “WordPress is not testable” then why bother about testable code at all?
Because writing testable code is the first step to testing your code, testing your code is the first step to testing ALL your code, testing all your code is the first step to reduce shipping times, reducing shipping times is the first step to fast response to feature requests and bugs that makes clients happy.
And because the first sentence is less true every day.
Let’s find a definition of “testable code” that applies to both WordPress and the current practices of testing; let’s see how we can stop ignoring the elephant in the room and embrace testing with a sane approach that improves code and coders quality without leaving anyone out in the cold.
I will present real-world examples of new and existing code, the tools used to write and maintain testable code and some simple rule-of-thumbs to keep in mind when developing for our beloved CMS.