Attivio is a huge fan of Atlassian Software and the Atlassian product suite as their products provide the foundation on which we've built our development process. Their upcoming Atlassian Summit will be a showcase of new features, product plug-ins, and practical implementation advice and customer stories. I'm very excited to have the opportunity to speak at the Summit and share our real-world experiences with Agile development and Atlassian's Tools.

My talk will cover Agile quality including our general approach to QA, and how we've used Atlassian's tools to build an integrated, efficient QA environment that produces very high quality releases. I'll break down our process into three main pieces: continuous integration, code coverage and unified testing.

Continuous Integration

Continuous Integration has become extremely common regardless of development methodology, but is absolutely critical to an Agile development shop. Continuous iterations of testing ensure that on any given day, our code is put through its paces and can be shipped on short notice. Atlassian's Bamboo product runs our continuous and nightly builds. My talk will focus on how we deploy Bamboo in our VMWare environment.

Code Coverage

Code coverage goes hand-in-hand with Continuous Integration - without sufficient code coverage, continuous integration doesn't provide much in the way of quality confidence. At Attivio, we require 80% code coverage before we ship. We determine coverage using Atlassian's Clover running as part of our Bamboo build environment. During the session I'll discuss some of the challenges we faced in configuring code coverage, and how we've integrated other coverage tools into our Clover reports.

Figure 1 - Clover Code Coverage Report

Unified Testing

Unified Testing is a name we put on something that has emerged pretty organically out of our dev process. What it means is that you run all tests in a common framework and provide a single point for reporting and investigating defects. We run unit, integration and installation system tests all from within Bamboo and produce JUnit-like output so that all test failures result in broken builds that we can investigate via the tight integration between our ticketing (JIRA), Build (Bamboo) and source code repository (SVN/Fisheye) systems. My presentation will cover how we built out our Unified Testing environment with a demo of how defects are reported and investigated.

Figure 2 - Integrated Installation Test Output

Figure 3 - Bamboo — Fisheye Integration

Figure 4 - Bamboo — JIRA Integration

As I mentioned before, I'm very excited to be able to share what we've done with the Atlassian customer community and am looking forward to getting feedback and new ideas.

I hope to see you there!

Attivio VP of Engineering Presenting at the Atlassian Summit

TrackBack URI for this entry

Comments (0)