I recently inherited a module to maintain that didn't have any testing structure setup. I'm no testing Nazi and have done a poor job adding tests to my other projects, but I thought I could do better with this project. While in Drupal 8 the focus is more on unit tests, in Drupal 7 Simpletests are the standard. 

The Simpletest module was born out the Simpletest PHP library. 

Something about the Drupal 6 contrib module...

Of the many new and shiny changes included in Drupal 8, one of the most significant additions in the spirit of "getting off the island" is using the Composer tool. Composer is a package manager that uses packagist.org to add and update your project's dependencies. 

I recently started trying to become more involved in the open source ecosystem. Previously, I had used a lot of community code and modules, but I didn't contribute much due to my lack of knowledge and expertise and not knowing where to start. Luckily, I started a job where I had a manager who maintained several modules and gladly gave me the reigns of one of them to maintain.

Adding behavioural testing to your project can do wonders for catching regressions, and even if you don't start out your development writing tests in true Behavioral Driven Development style, you'll greatly benefit from having this type of test coverage. 

In today's world, users are accustomed to having results personalized for them without having to do any work. If you login to your favorite store, e.g. Amazon, you'll get a list of recommended products. Google will provide you location-based searches. Your video streaming services, banking, big box stores, even your potential online dates all have incorporated location-based way-finding. Sometimes, you aren't even aware that you are being directed by location. 

Let's be honest, I don't really like the Quicktabs module. It's not that I don't think it's useful, it's just that users can do some pretty gnarly stuff with it that causes issues, like a ton of PHP notices being thrown into logging.