This post is part of a series of blogs on Atlassian QA. We will cover how the QA strategy has been implemented in different teams, the tools and techniques we use, and the personal experiences from members of the team.
The JIRA engineering team is large, consisting of 78 developers and team leads, 10 product managers, six UI designers, and three technical writers. To assist this vast crowd with quality, we have a team of only six QA engineers.
In Introducing Atlassian QA, we described the overall

On the Atlassian Marketplace team, we have a daily standup at 10:30 a.m Pacific. With one permanently remote team member, we were having to manually start a Google Hangout on the wallboard every morning. To make matters worse, our standup music was played by a small app which pulled the wallboard out of fullscreen mode. I took it upon myself to automate the wallboard and standup hangout completely within the browser, so in my spare time I wrote Crontabs.
Crontabs is a simple Chrome extension

You've probably heard about the awesome workflow capabilities that Git can offer you. But you may be asking yourself, "How can a version control system that just stores my code history really be that helpful?" The answer is all in the workflows. For many teams, some of the most pressing development questions can be addressed with a proper workflow:
Are all the features completed for the next release? Are we missing any commits?
Has everybody reviewed the new code?
Does every team member know

Every quarter, Atlassian holds an event called ShipIt. Essentially, the whole company stops work for 24 hours (usually a Thursday and Friday) to form teams and compete to build kickass products, plugins, or features.
For ShipIt 25, Patrick Teen, Jason Sheehy, and I decided to tackle the visitor sign in app at reception here in Sydney. The current sign in experience (an iPad with a rather ugly app) has been the target of much critique from the design team.
Anyone who visits the Atlassian

This is the first in a series of blogs on Atlassian QA. We will cover how the QA strategy has been implemented in different teams, the tools and techniques we use, and the personal experiences from members of the team.
True, it's an assumption – but probably a safe one – that the majority of professional software testers can't code. This seems to be the cause of perennial hand-wringing by some testers who feel the need to justify their lack of technical skills, and frustrated developers who

If you've ever sat down with a more experienced developer for a pair programming session, you'd probably agree that it's one of the most effective ways to learn, and absorb new skills, tools, and tricks. So I am very happy to present you with a new webinar that will reproduce the same feel of a live training session. This is your chance to sit beside me as I work through a typical bug-fix lifecycle from branch creation, through code review, to the final merge, using the powerful toolset that Git brings