Test Management Tools for Agile Projects: QASymphony

Test Management Tools for Agile Projects: QASymphony

Do you want to find a test management tool for agile projects? Looking for an easy way to improve speed and efficiency in your testing lifecycle? To explore how to make software that works, I interview Lewis Lovelock, Test Product Specialist at Clearvision.


Finding the Right Test Management Platform

Lewis’s Story


About five years ago, Lewis was (in his own words) bad-haired, spotty and straight out of an IT apprenticeship, knowing little of the modern IT business and even less about test management tools for agile projects.

Today, not only is Lewis a Microsoft Certified Solutions Associate, he’s also proudly the Test Product Specialist at Clearvision, working on our partnership with QASymphony and the qTest platform.

Let’s dive straight in.

Angela B: What is qTest? Give us the two-minute pitch.

Lewis L: qTest is a test management platform for agile projects that helps companies create better software by improving speed, efficiency and collaboration during the testing life-cycle.

It comprises five different tools:

  • qTest Manager – Our main test case management offering, with built-in workflows for teams that release software less often than once a week.
  • qTest Explorer – Manual testing tool (exploratory and scripted) that records data of a testing session and automatically creates detailed documentation.
  • qTest Scenario – JIRA app to help progressive “shift left” testing teams scale test-driven development (TDD), behaviour-driven development (BDD) and acceptance test-driven development (ATDD).
  • qTest Pulse – For those wishing to practise more DevOps with built-in workflows for teams that release software continuously (at least once a week).
  • qTest Insights – Business Intelligence and data analytics engine, providing central reporting on all testing activities across the platform.

AB: Can you use any of the qTest products to facilitate your automation?

LL: Kudos to the eagle-eyed of you who noticed I haven’t yet mentioned automated software testing! Well, if it ain’t broke, don’t fix it.

We know other tools are so popular and do their job so well, we’d waste our time even trying to replace them. Instead we’ve made it so you can easily integrate them into your qTest platform.

AB: Why qTest?

LL: Arguably lagging behind the rest of the software development lifecycle in terms of adoption, testing is slowly evolving out of the dark ages and into the agile light.

The legacy of HP Quality Centre (HPQC) and its waterfall methods still dominate the industry, while the Micro Focus acquisition of the tool leaves many testing teams with a lot of questions about their uncertain future.

Twitter Logo“Test quality in, not bugs out” – Lewis Lovelock @clearvisioncm” –Click to Tweet

However, this is where I believe QASymphony and the qTest platform can fill the gap.

From teams that want to remain waterfall and simply replace HPQC cheaply, to those already releasing continuously, qTest has tools to facilitate all aspects and evolve with your testing team as they do.

Want to continue the discussion? Contact Lewis today to talk about the qTest platform and how it can fit into your team.

AB: I know that qTest integrates with JIRA. What other software development tools does it join with?

LL: We have integration with Jenkins and Bamboo build tools straight out of the box! For those needing automation support, there are API integrations for Selenium, HP UFT, TestNG, Cucumber and more.

For agile teams using an ALM for managing their requirements, we also support integration with JIRA, Bugzilla, Rally, VersionOne and Fogbugz.

AB: We hear a lot about DevOps lately. What do you think it means for testing teams?


The ability to release well-tested software quickly and often is key. Testers working together with developers to achieve this is going make this possible. qTest Pulse is the tool that is going to help best do this.

qTest Pulse works automatically in conjunction with your chosen build tool and version control systems (VCS) to make sure you only release your software once it has satisfied all your manual and automation tests, while making sure you are able to release quickly and often.

AB: Moving forward, where should your testing team start?

LL: Well, that’s where I step in and liaise with real testing teams to understand their needs.

If you wish to discuss anything about the qTest platform and how it can fit into your team, contact me at llovelock@clearvision-cm.com – I look forward to hearing from you!

What do you think? Have you used other test management tools in your software development? Please share your thoughts in the comments below.


Reader Interactions

Related blog articles

    Reader Interactions