Drupaldelphia is an annual all-day event held in Philadelphia as part of Philly Tech Week. The event focuses on Drupal and gives developers, site-builders, content administrators, designers, and others from the Philadelphia area the opportunity to participate in and attend sessions, sprints, labs, and workshops.  

This year, we were a core sponsor of the event, and many of our Probo team members led sessions!

There is increasing pressure for software developers to develop features and products that provide customers with everything they want. On top of that, there is a need for these products to be delivered on time and under budget.

It’s for these reasons that developers are turning to continuous testing. As we’ve mentioned in previous posts, continuous testing differs from traditional testing because it occurs earlier and more often in the development lifecycle.

During traditional software development, it isn’t uncommon for development and operations teams to work in silos. Silos limit cross-team communication until the very end of the software development project. 

This means that throughout the development cycle, developers only work on developing and operation teams only focus on operations. This method of software development is less than ideal and leads to reduced productivity. 

This is the final blog entry of a three-part series that we started about shift-left testing. 

Part one of this series introduced shift-left testing and the concepts and methodologies behind it. You can read more about the history of shift-left testing, here. You should also check out part two of this series which explained the benefits of shift-left testing. 

This is part two of our shift-left testing series. A few weeks ago, we released part one, which explained the concept of shift-left testing and provided an overview of its methodology and history.

The shift-left testing methodology moves the testing part of web development closer to the beginning of the process instead of leaving it at the end. When you shift testing to the left it ensures that developers are testing earlier and more often.

Your team might consist of a number of expert developers who consistently produce high-quality work, but if they don’t communicate well, your projects will inevitably experience regular hiccups. Prioritizing communication and collaboration is just as important as implementing high-quality standards. Incorporate the tools and suggestions below to create a more open and transparent development workflow and get all of your team members on the same page.