Thorsten is a certified PHP engineer, web development professional and tester. He is working in the web since 2000, and with (and on) WordPress since 2005. Currently, Thorsten is a WordPress engineer and technical project lead at Inpsyde, Germany’s biggest WordPress agency. He is part of Inpsyde’s QA team, and leads the development of MultilingualPress, the multisite-based free open source plugin for your multilingual websites. Thorsten also maintains WP REST Starter, a Composer package for working with the WordPress REST API in an object-oriented fashion.
Who Is This Wes Bos?
At the end of last year, I had a straightforward, easy-to-understand and even partly visual answer to the question who Wes Bos is.
@wesbos in a nutshell:
['', '', ''].map();
// ['', '', '']
— Thorsten Frommen (@thorstenfrommen)
A detailed explanation of unit testing for WordPress, with examples for setting up tests in a variety of explanations. Plus it has Lego in the featured image! :)
Thorsten is a web developer since 2000, working with (and on) WordPress since 2005. Currently, Thorsten is a WordPress engineer and technical project lead at Inpsyde, Germany’s biggest WordPress agency. He is part of Inpsyde’s QA team, and leads the development of MultilingualPress, the multisite-based free open source plugin for your multilingual websites. He also maintains WP REST Starter, a Composer package for working with the WordPress REST API in an object-oriented fashion.
Thorsten is a certified PHP engineer, web development professional and tester.
If you are a software developer, you might have come across the term “testable code”. But what is it? What makes code testable, and what not?
Every piece of software is testable—somehow. There are several things you might be able to test:
the return value of a function;
the output of a function;
other side effects of executing a function;
whether or not a program crashes;
So, doesn’t that mean every piece of code is testable code?
It does not. That’s because almost always when someone refers to “testable code” they do it in the context of unit testing. So
A really great WordCamp recap post. WordCamp organizers should have a platform to publish these somehow and make them official.
This weekend, WordCamp Nijmegen happened. While having been my eleventh WordCamp in total, and my eighth time as a speaker, it was the first ever city-based WordCamp in the Netherlands. And it was awesome! Thursday: The Day Before
WordCamps usually start quite early in the morning. Since not all attendees of a WordCamp live in the according city, a lot of them—me included—oftentimes schedule their arrival on the day before the first WordCamp day. These days before are a good opportunity to grab dinner and a beer together, and start boost your community adrenaline.
This time, however, I could leave only pretty late in the day. When I finally made it to my hotel, I was too tired—and I nevertheless had to work on my slides anyway. So no pre-event for me this time.
Luckily, this was not the case for everyone, so there did happen some inofficial get-togethers.
Friday: Contributor Day
WordCamp Nijmegen started with a contributor day, and also with a great amount of first-time contributors.
As every so often, I started contributing by looking through my open tickets on Trac. There was one ticket catching my attention that also has a patch since day one—which