Your transformation toolkit

Advance your enterprise testing strategy with our transformation toolkit.

Learn more

Agile testing

Top 7 agile testing questions from Atlassian Summit 2019

We just returned from sponsoring Atlassian Summit for the 5th year in a row. As always, it was a blast chatting with countless agile teams looking to scale their testing with Atlassian Jira software. From Expo Hall open to close, we had non-stop conversations about optimizing Agile testing workflows. Throughout the hundreds of great discussions, 7 core themes about software testing trends and Jira integrations emerged as attendees’ most pressing questions and concerns. Here’s a quick recap of those top attendee questions, as well as our responses:

1. “Why Can’t I Just Use Jira for Test Management?”

You can, but Atlassian doesn’t recommend it.  Although Jira is the leading solution for enterprise agile planning, it’s not optimized for performing test management. That’s why Atlassian recommends that teams should either look at native Jira testing apps like Zephyr for Jira, or integrate with an external test solution like Tricentis qTest.

2. “What’s the Difference Between Tricentis qTest and a Jira Testing App?”

Once teams recognize the value of extending Jira with a complementary test management solution, the most common question we hear is, “What’s the difference between Tricentis qTest and Jira testing apps?” As mentioned above, there are really two viable options for Jira test management:

  • Integrate with Jira via a third-party testing app (I.e. Xray, Zephyr for Jira)
  • Integrate with Jira via a third-party standalone solution (I.e. Tricentis qTest)

At first glance, using a third-party testing app might seem to be the best option. These apps provide a native Jira experience, and they’re good for some teams with heavy manual testing and little test automation. However, neither these apps or legacy solutions like Micro Focus QC/ALM effectively scale to support enterprise test automation workloads and integration needs [see case studies]. That’s why so many enterprises find that adopting Tricentis qTest is a critical step in getting the most out of their investment in Agile and Jira adoption.

3. “How does your tool integrate with Jenkins, Bamboo, Selenium, etc.?”

Besides integrating with Jira, Tricentis qTest also provides extremely easy and flexible integrations for your DevOps delivery pipeline. Whether you’re using a popular framework like TestNG or you’ve built your own custom Java framework, qTest can schedule, execute, and report across any automation scenario.

qTest also enables you to schedule testing without slowing down the performance of your Jira instance. At the booth, we demonstrated how easy it is to integrate test results from Jenkins freestyle and pipeline projects via a free plugin.

As a quick use case, check out how Dolby Labs integrated their test automation with qTest and Jira.

Dolby Labs | Scaling extreme test automation for API, SDK, UI
  • Scaled monthly test activity to 153 platforms tested, 422 builds & 300,000 test runs
    • Reduced test run reporting from hours to minutes
    • Scaled the number of test runs executed from 45 to 7,000 per minute

4. “We’re using Quality Center, but it’s not working with Jira—how do you integrate with Jira?”

This is our favorite question to answer! You can spot a Quality Center user from a mile away. They approach with a gloomy face and solemnly ask, “How the heck do I get off QC?”

The majority of customers that we interact with have become exhausted with the waterfall nature of Quality Center and struggle integrating QA with their agile push to Jira. We spoke with multiple system admins who described the pain of Quality Center’s scheduled sync, which results in constant data delays and maintenance.  

The good news is that qTest offers an entirely different approach to Jira integration. qTest’s real-time integration with Jira Cloud, Server, and DC leverages web-hooks: Atlassian’s best practice method of integration. That means data that’s always up to date — including requirements, defects, release planning and more— and no more delayed data syncs.

Ready to switch from Quality Center? Contact us today for a free qTest + Jira demo.

5. “Can You Manage Testing with Multiple Jira Instances?”

If you’re a large enterprise, chances are that you have multiple Jira instances due to mergers and acquisitions, or teams running their own projects in silos. As teams look to consolidate on a unified Jira instance, testing still needs to continue without interruption. That’s why qTest allows teams to map their qTest platform to multiple Jira instances.  This comes in handy when companies don’t want to purchase separate Jira testing apps for each Jira system.

6. “How Do You Help Teams Scaled Agile and Reporting?”

Reporting test progress at the team, program, and portfolio level can be challenging, especially when you’re scaling agile. It’s no surprise that we had tons of questions around:

  • How do I report my test automation progress?
  • Where can I see a roll-up of test progress for my portfolio?
  • Is there a way to see ‘at risk’ user stories in Jira?
  • Can I share executive reports with stakeholders outside of our development systems? (I.e. Confluence)

We had an entire booth section dedicated to answering these types of questions. For the team level, qTest integration can report test results directly on Jira issues; this way, developers and product managers can readily see which issues are ready for release.

For the program level, qTest insights provides executive dashboards for projects that are functionally related.

Lastly, for the portfolio level, we can string together like-minded projects that share budget and resources to highlight holistic enterprise test progress for true portfolio visibility.

7. “How Do You Support BDD and Jira?”

Another hot topic this year was incorporating BDD with Jira. This is no surprise since BDD adoption has grown from 10% in 2016 to 17% in 2018. Most BDD teams follow a best practice branching process where the feature files and supported code are not merged to their master branch until their feature branch has been reviewed and approved. This works especially well when you label your feature branch after the Jira User Story ID.

When attendees had this use case, we showed them how qTest Scenario —  Enterprise BDD for Jira — integrates with Jira issues and helps you save feature files to specific branch locations. This enables teams to work on feature files outside of their master branch, test their scenarios, and then move the feature files to their master branch for the production release.

The Continuous Testing Platform for Jira Software

Tricentis qTest’s real-time integration with Jira releases, issues, and defects allows agile teams to plan, track, and execute their test automation strategies faster than ever before. Learn more about qTest and Jira from the resources below.