Modernizing The WordPress Toolbox
summary
WordPress updates its build and test stack: it keeps core.svn but adds a develop repo and git mirrors, adopts grunt and CI (Travis CI), and ships tooling like grunt-patch-wordpress to apply patches with one command and grunt-cssjanus / grunt-rtl-css for RTL CSS. Tests move into the same repo and unit coverage jumps from 136 new assertions to 382 assertions in eight months; JavaScript gets QUnit and JSHint; the changes increase transparency, double test additions, and actually simplify contribution workflows for 283 contributors.
AI-written summary · about
chapters (26)
- 0:00Start
- 3:25Simple Test
- 5:19Options Options
- 5:53Bots Behind the Scene
- 6:58Tests are Harder
- 7:51Philosophy of Tooling
- 8:03Make Contributing Code Easy
- 8:58Barriers Only On Purpose
- 14:57Version Control Agnostic
- 18:06Build Our Own Tools
- 18:42Simplify Steps
- 22:59Grunt- RTLCSS
- 23:37Team Effort
- 24:31PHP Code Sniffer?
- 24:54Blame is a debuggers friend
- 26:17Minification Bugs
- 26:53Tests & Code Same Commit
- 28:17Mocha QUnit Jasmine
- 29:49Better Patches
- 34:37Command Line WordPress
- 34:53Varying Vagrant Vagrants
- 36:01Lessons
- 36:15Have Goals
- 37:54Learn from yourself
- 39:42Support
- 40:25You Own Your Dependencies Bugs
