I love WordPress. I also love MVC design fundamentals. Unfortunately, these two loves of mine are at odds with one another, and that makes me sad. Here’s my simple idea to make WordPress’ built-in templating engine play nice with MVC sensibilities – everyone can win!
After watching a few sessions of WordSesh – particularly the podcasting roundtable – I’ve decided to take another stab at podcasting. This time around I want to cover a broad range of topics, and throw in some video. I’m asking for the community’s help getting this show off the ground, and I won’t be able to get things started without your help!
Determining which methods in your application needed testing used to be easy – test everything exposed by the public API. But once you invite other developers to contribute, you are exposing a whole other set of internal APIs to the team. The behavioral consistency of these methods is just as important as that of the public API, so shouldn’t you be testing them too? I would argue you should, even if this internal API consists of private and protected methods. To make life easier, I’ll give you a couple of tools for testing these limited-visibility functions without forcing everything to be declared “public.”
Today is my birthday, and also marks the completion date for my previous “to do before I reach a certain birthday” list. I’m asking for your help in building my list for the next however many years.