Say hello to JIRA Agile and JIRA Capture Learn More »

Archives for the tag: testing

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

Continue reading »

Guest blog: UI tests say more with JIRA + Jubula

Today we have a guest post from Alexandra Schladebeck, product manager for Jubula, an Eclipse open source project for cross-platform, functional test automation. Alex and her team use JIRA every day to manage their work, and got so excited about it, they couldn't resist writing an integration. Why do we test? Without getting too philosophical about it, I like using this definition: “We test to gain information so that we can make decisions”[1]. That fits especially well with agile processes,

Continue reading »

Guest blog: test management for agile teams

I'm speaking at RoadTrip 2014 Learn More »

This is a guest blog post from Zephyr, makers of Zephyr for JIRA. The value of test management software in agile development Today's software developers and quality assurance teams face far different challenges than their predecessors. Balancing the need for speedy development cycles with the desire to keep costs down has led software developers to place more focus on their communication capabilities and foster collaboration among remote teams. Agile development was supposed to better address

Continue reading »

One of the greatest things about our software development process is our need and desire to test everything. Unfortunately, this doesn't always translate into absolute best practices in the test code, coverage, or design, but we are always improving. Something I have been been meaning to get around to is property based (or automated specification based) testing. The traditional approach to unit testing (and TDD) is to write a test, see red, and then go fix it. If doing TDD religiously, this can

Continue reading »

Or "I don't have TIME to understand Maven; I've got work to do!" A big part of developing a plugin is seeing it work inside the base product. For JIRA plugins, this is accomplished using the maven-jira-plugin. There are two options for getting your plugin to run inside the host application: adding it as a bundledArtifact, or as a pluginArtifact. If you examine the configuration of an established plugin, like GreenHopper or any of JIRA's bundled plugins, you might see multiple plugins

Continue reading »

Whilst trying to TDD a bug fix, I hit a problem stubbing Stash's NavBuilder. Stash uses NavBuilder to generate hyperlinks to different areas in the application. NavBuilder uses a hierarchy of builders to give developers a fluent interface for link creation.  For example, building a link to a pull request looks like this: [cc lang="java" line_numbers="0"] navBuilder.repo(repository).pullRequest(pullRequest.getId()).buildAbsolute() [/cc] Stubbing with mocks in the traditional way requires

Continue reading »