What’s New in qTest 9: Webinar Recap

Yesterday, QASymphony’s Ryan Yackel and Elise Carmichael hosted a webinar to walk through the latest features in qTest 9, a major update to the qTest platform that was released last week. If you missed the webinar yesterday, you can watch the recording here:

Watch the qTest 9 Release Webinar on demand

Yackel noted that with this release, qTest has taken a major step towards becoming a central hub for QA and development teams to organize, manage and perform all things test-related, whether it’s manual, automated, performance or exploratory testing.

That’s because with qTest Launch, QASymphony is changing the way organizations approach and structure their test automation strategies, Yackel said. qTest Launch provides a single interface for managing test automation across frameworks and tools. qTest Launch can be used to schedule and run automated tests, configure test machines, schedule tests and report on results. Because QA teams don’t have to separately kick off tests on various machines, this can be a huge time-saver.

There’s been lots of demand in our customer community for a tool that centralizes test automation strategies, so it’s no surprise that our poll showed this is the feature that webinar viewers said they were most excited to use:

qTest 9 webinar poll

In fact, Janice Bethke, who is Director Quality and Process at Life Time and participated in the qTest Launch beta program, told us she was looking forward to trading a Jira add-on for a more scalable solution. “Before, we were using a Jira test management add-on that could no longer accommodate the growing number of automated tests we were running in each three-week sprint. After participating in the qTest Launch beta program, we are excited to roll out the product across all of our test machines to help streamline management of the thousands of test runs we do every week.”

During the webinar, Carmichael demonstrated how, using the qTest Launch scheduler, you can quickly set up the same agent on multiple machines, instead of having to go to each machine to install the agent. She also demonstrated bulk editing capabilities, which allow you to make global changes to agents across hosts, add or delete tags and modify polling frequency.

Next, Yackel and Carmichael provided an overview of the second major piece of the qTest 9 release: qTest Scenario Enterprise. In Yackel’s words, qTest Scenario Enterprise “helps everybody get on the same page with behavior-driven development (BDD).” He noted that because BDD provides an easy way to understand how business requirements are translated into technical requirements, it offers an ideal way to get started with automated testing. The foundation for the automated tests that are written are in plain English, which helps keep everybody on the same page, from business leaders to product owners, developers and testers.

However, a lot of teams struggle to get started with BDD, Yackel said. qTest Scenario Enterprise is designed to facilitate the process change. By connecting with Jira, teams can connect directly to requirements, and by connecting with source code repositories, they can use source code as their source of truth. In that way, qTest is the glue that connects all of the pieces of behavior-driven development.

One of our customers, a Fortune 500 company in the investment space, recently told us about the challenges they faced in adopting BDD. According to this customer, “We are going through a culture change. A lot of us are doing BDD and want other departments to follow up in this journey. We’re using qTest scenario to help us with our process transformation.”

Next, Carmichael demonstrated how to create a BDD test scenario in qTest Scenario. She saved the new feature file in Scenario, which went straight to Bitbucket. Then, when new code was submitted to Bitbucket, it automatically notified qTest. By setting a rule with the qTest rules engine, anytime a new snippet of code is entered into BitBucket, qTest will be triggered to run a Jenkins test, parse the results, and then upload them to various places, based on how the rule is set up. In this example, Carmichael had notifications sent to both Slack and qTest Manager. qTest Manager automatically created a test case that was linked to the source code.

The webinar also reviewed some significant enhancements to our Jira integration that were part of our recent qTest 8.9 release.

To see qTest 9 in action, watch the webinar recording

Leave a Reply

Your email address will not be published. Required fields are marked *

More Great Content

Get Started with qTest