Archives for the tag: qa_innovation

QA test data is now available for Confluence Plugin Developers

Introduction This is test data which is useful for finding issues with Confluence features and plugins. If you are a plugin developer, you should use it. Test data - why it is useful Developers tend to perform testing as users called "Test User" and use pages called "Test Page" QA Engineers are looking to find problems, and we know that it is more effective to use more 'challenging' test data. This may include unicode characters, lengthy titles, XSS strings, etc. We also tend to use non-standard

Continue reading »

Tags: , , , , , ,
Comments (1)

Equivalence Partitioning in Practice – Part 2

Introduction Yesterday in Part 1, we looked at what equivalence partitioning is and how we use it in JIRA QA. In Part 2, we will cover how equivalence partitioning might explain some odd behaviour you've noticed from your friendly neighbourhood QA/test engineers. Explaining QA behaviour Here are some symptoms of equivalence partitioning that you may have noticed: We want to know how things work When I first transferred onto the OnDemand project, it initially involved taking our existing JIRA

Continue reading »

Tags: , , , ,
Comments (2)

Equivalence Partitioning in Practice – Part 1

The Challenge When testing even the most basic user-facing functionality, the set of possible test cases is almost unlimited. Let's say we're testing a form in JIRA where you set the current user's display name. If we look at it from a completely black-box perspective, the possible test cases are something like: Total test cases = (supported browsers) x (supported platforms) x (supported databases) x (JIRA licence types) x (OnDemand/Standalone/War/Windows installer/OnDemand-with-JIRA-only) x (different

Continue reading »

Tags: , , , ,
Comments (0)

Bonfire 2 Deep Dive: Shared Sessions & Blitz Testing

Atlassian Bonfire 2 makes it easier than ever to collaborate with teammates around test activity. Software development involves the entire company, and collaborative testing is one of the ways Atlassian connects people across teams working together to make better software. Share & Join Sessions Bonfire's Test Sessions are the central place in JIRA to track testing of a specific requirement or defect, and now when you create a session, you can mark it as shared. Once you start the session, anyone

Continue reading »

Tags: , , , ,
Comments (2)

What’s your Testing Mission?

Sessions are a great and simple way to organize testing tasks. They are nothing more than dedicated time to test a feature with the intent of fulfilling a mission. In fact, because the division of a task into smaller pieces is so intuitive, we often forget the importance of the mission itself. In this blog post I will talk about different types of test missions to keep in your arsenal and how you can leverage them in your testing. I assume some knowledge of what is exploratory testing and the

Continue reading »

Tags: , , , , ,
Comments (0)

QA Innovation Blog Round-Up

We've learned a lot from the submissions to our 13-part blog series raising awareness about testing innovation within the QA community. Today we're excited to announce Bonfire 2, with new features to connect teams and testers and foster collaboration, so now is a great time to take a look back at everything we've heard so far. You can find all the posts in this series under the QA Innovation tag. We started with a recipe for innovation success from our own Andrew Prentice, QA lead at Atlassian.

Continue reading »

Tags: , , , , , , ,
Comments (3)