To my knowledge, Longhorn PHP was the only new PHP community conference in the US that I didn’t get to speak at last year — I was fortunate enough to speak at PHP Detroit (Detroit), Southeast PHP (Nashville), Cascadia PHP (Portland), and WavePHP (San Diego). In fact, I haven’t been outside of an airport in Texas since the final Lone Star PHP (the spiritual predecessor to Longhorn PHP) in 2017. That’s but one reason I’m excited to announce that I’ll be giving my Testing Like You’ve Never Tested Before (Because You Haven’t) talk at Longhorn PHP 2019!
Tag: Testing
I’ve been fortunate enough to speak at most of the community PHP conferences across the continental United States (that can pay for travel, anyway), with one notable exception: Midwest PHP. That’s why I’m thrilled to announce that list will be one shorter this March, as I’ll be giving two talks at Midwest PHP 2019!
This January, I’ll be kicking off the new year giving my second-ever Nomad PHP talk: Testing Like You’ve Never Tested Before (Because You Haven’t).
For the first few years of my speaking career, I viewed CodeMash as something of a White Whale; after all, the conference regularly brings in some of the best speakers in the industry, convening on the Kalahari at the beginning of the year like some sort of geeky New Years’ party. In 2017, I was lucky enough to give my first talk at the conference. Attendance was, well… let’s say “underwhelming”, but the experience of speaking at CodeMash was great.
This year, I’m proud to announce that I’ll be kicking of 2019 by speaking at CodeMash again! I’ll be giving my Testing Like You’ve Never Tested Before (Because You Haven’t) talk, which serves as an introduction to automated testing.
In every testing talk I’ve attended (or given), there’s one stand-out feature that often has the audience saying “whoa, I had no idea you could do that!” No, it’s sadly not “hey look, you can reliably build quality software with a much lower chance of defects or regressions!”, but rather the inevitable use of PHPUnit’s Data Providers.
With Data Providers, our test suite can become more readable and maintainable while making it trivial to add new testing scenarios. Best of all? PHPUnit ships with Data Providers right out of the box.
I’ve long considered WordCamp Kent (formerly WordCamp Northeast Ohio, and WordCamp North Canton before that) to be the premier WordCamp in Ohio. Don’t get me wrong, I had a lot of fun in Cincinnati last year, WordCamp Dayton always puts on a good show, and Columbus will always be my first (and hometown) ‘Camp, but Kent has been the highlight of my Ohio WordCamp experience for the last few years.
WordCamp NEO (2016) marked the first time the conference was held in Kent, Ohio, along with the first time I got to formally meet Chris Lema (my current boss); I’d be lying if I said the session I spent sitting into the hall talking to Chris didn’t in some way lead to me being at Liquid Web today. Then I spent the after-party having a great conversation with podcaster, educator, and generally funny (lookin’) Adam Silver. Last year, I got to know WordPress educator and freelancer Carrie Dils along with SEO expert Rebecca Gill (who wasn’t even speaking, she just wanted to take in the fun). Kent consistently pulls in big names for a moderately-sized WordCamp, meaning you’re able to really get to know the speakers and attendees.
If you haven’t heard, Liquid Web is now the first company offering Managed WooCommerce hosting, which is a huge step forward in the world of WordPress-oriented e-commerce. As a result, I’ve been spending a lot of time over the last few weeks working on WooCommerce extensions that help improve the experience and performance of WooCommerce.
One of the main WooCommerce extensions I’ve been working on is WooCommerce Custom Orders Table, which takes the WooCommerce 3.x CRUD concept to its next logical point: storing order data in a custom, flat table instead of scattered throughout post meta. Mindsize worked with other members of my team at Liquid Web to build the initial version of the plugin, then I came in to fix a few bugs.
In a perfect world, every piece of software would have automated tests. As soon as we change a line, we as developers would know what, if anything, broke in our application and where we need to look to fix it. Unfortunately, we don’t live in a perfect world, so we get by doing what we can.
Still, we can look to our image of the perfect world and draw from it, molding and shaping what we do have to closer resemble what we’ve been longing for.
![php[tek] 2024 logo](https://stevegrunwell.com/wp-content/uploads/2024/02/phptek-2024-150x150.png)