Archives for the category: Developer

(Guest blog) Interviewing the Product: Making Testing More Flexible with a Heuristic Test Strategy Model

This guest blog post is part of an Atlassian blog series raising awareness about testing innovation within the QA community. You can find the other posts in this series under the QA Innovation tag. The post is written by Michael Larsen, a "Lone Tester" with SideReel.com, which is a division of Rovi Corporation. His experience covers networking equipment software, SNMP applications, virtual machines, capacitance touch devices, video games and distributed database applications/web services. Processes

Continue reading »

Tags: , , ,
Comments (0)

The Kaizen Project – Continuous improvement for your Agile team

is a new source of information to assist Agile teams in continually improving their practices and processes. Kaizen is the Japanese word for 'improvement' and The Kaizen Project shares best practice stories from around the globe. Topics from innovation to continuous deployment are covered, along with everything in between. Teams at Atlassian are always looking for, and finding, new ways increase velocity, improve quality and deliver more frequently. Find stories from these Agile teams on The

Continue reading »

Tags: ,
Comments (0)

Testing and Bad Smells: When to Investigate Potential Bugs

This guest blog post is part of an Atlassian blog series raising awareness about testing innovation within the QA community. You can find the other posts in this series under the QA Innovation tag. A condensed version of this post was published on January 10, 2012. We're now reposting the complete article. Something Smells Fishy You're testing a feature, and along the way you spot something that seems unrelated and trivial. Maybe it's a warning message in the logs that wasn't there before. Or some

Continue reading »

Tags: , , , ,
Comments (4)

Lo-fi wallboard lets you view build status in the cloud

Here at Atlassian, we have wallboards everywhere. On my team, we have a wallboard that cycles through screens showing the build status, the number of open JIRA issues assigned to team members, how many pending code reviews we have, and relevant deadlines. We recently had a FedEx day. FedEx days are a chance for developers to work on a project of their choice. Generally these projects are software - new plugins, spikes or products. Anna and I are Confluence developers with a distinctly crafty

Continue reading »

Comments (2)

Fedex 18 – The Winners

While we think all our fedexers are winners, the finalists in the 18th edition of Fedex were more winners than others. 1st Place Don Willis, Ryan Ackley, Wesley Walser, Chris Mountford and Alex Wei carried home the glory with the aptly named Awesome Paste for Confluence. In their entry, they implemented an editor plugin to transform a pasted URL into a neater format. In fact, we liked it so much we included in Confluence and called it Autoconvert. Other finalists Chris LePetit and Robert

Continue reading »

Tags: ,
Comments (0)

Scanning Confluence for Content Errors

Introduction As technical writers working on a wiki, one of the problems we face is that Confluence doesn't really have any in-built feature for detecting a range of content errors. I refer to things like broken internal links, broken images, broken JIRA issues macros (specifically), any macros that have failed to render (in general) and inclusions that cannot find the page to insert (covering {include} and {excerpt-include} macros). Some other problems are that you tend to end up with a lot

Continue reading »

Comments (11)