Over the past two years we’ve been pushing to improve our automated testing practices within Plusnet and to win full support for it within the company across the spectrum of fellow developers, project managers and upper management. It took a while to agree on software we want to use, and standards we want to follow, but now all new code is being continuously built and tested and the results of that are visible business-wide. We use PHP_CodeSniffer to verify that we follow our coding standards, PHPDocumentor to generate automated API documentation, PHPUnit to run test suites and phpUnderControl to run all these tools regulary, at least once a day and to generate aggregated reports. Finally, Sonar allows us to create and publish reports visible to everybody and more importantly reports that everybody can understand. Setting it all up can be a tough exercise, but if you prepare to it upfront you might actually find it quite exciting! So, you strongly believe this is the way you should be developing your code, but you don’t really know where to start? Let me show you how our journey began. You don’t know how to convince your fellow developers to follow you? I’ll tell you how to establish a strong team that will follow you. Your managers seem to be more interested in delivering your project on time and don’t really see a point in spending additional time on unit testing and documenting your code? Maybe you haven’t shown them the benefits of continuous integration in a way they can understand. I’ll show you what worked for us.


Comments are closed.

Really nice introduction into continuous integration - tough subject - everyone knows that it exists but just couple use it.

Rated 1

Anonymous at 22:49 on 4 Apr 2011

najbardziej obsysający punkt programu. autopromocja w mdłym stylu.

The first minutes of presentation I can summarize as: "Ymmmmm, ...., Ymmmm ';) - Sebastian seemed to be a bit stressed out, which could be heard in his voice. However, after a few minutes, Sebastian calmed down and led a really good presentation about introducing CI in his company - based on their own experience and tools used. So he mentioned SimpleTest, PHPUnit, phpUnderControl, PHP_CodeSniffer, Depend PHP, PHP Mess Detector, Sellenium, Hudson / Jenkins and Sonar - variety of tools, whose use leads to write better code.
Sebastian drew attention to such things as: identification of a single coding style and stick to it consistently (e.g. - if the code does not meet standards, it is moved back to the developer for the fixes), or about how much programming in pairs gives you, even if it takes 30 minutes per day.
In conclusion - successful presentation - gave me motivation to try the CI within your own team:)