With the release of Tricentis qTest 9, Tricentis has added two new tools to the qTest Platform: qTest Launch for test automation management and qTest Scenario Enterprise for streamlining behavior-driven development. These tools deliver new ways for development and QA teams to accelerate software test cycles and reduce time to market. Both tools are available to Tricentis customers now through the qTest 9 platform update.
qTest Launch enables development and QA teams to scale test automation with a single interface for scheduling and running automated tests, configuring test machines and reporting on all scheduled tests. With qTest Launch, testing teams can centrally configure and manage automated testing across automation frameworks and tools.
Key features of qTest Launch include:
- Centralized test automation: Execute all automated tests from a single interface, kick off tests individually or in bulk and centrally maintain all test machines and configurations.
- Integration across frameworks and tools: Leverage any open source or proprietary framework or tool, from Selenium and Appium to Cucumber, Junit or Unit Test frameworks, to Postman, Jmeter or Neotys. Use your own test machines or execute tests against an emulation service such as SauceLabs, all while maintaining centralized control.
- Enhanced visibility: Track automated tests across multiple machines, quickly access the latest test automation run results and drill down into the status of specific projects with filters and customizable dashboards.
- Increased test automation coverage: Tie automated test results directly to business requirements through an integration with Jira, and quickly determine test coverage with status traceability to each requirement.
Today’s QA teams are automating tests using a wide variety of automation frameworks and tools, many of which are open-source. While this offers tremendous flexibility to organizations leveraging automation to reduce testing time, the lack of a central location for configuring, managing and analyzing the results of automated testing have been a roadblock for many organizations who would like to take advantage of these tools. As our CTO Jonathan Alexander noted in the qTest 9 press release, qTest Launch enables these organizations to centrally manage automation machines, tools and tests, so they can scale their automation strategies and ultimately reduce time to market.
Janice Bethke, Director Quality and Process at Life Time, participated in the qTest Launch beta program to explore how she could scale Life Time’s test automation strategy. “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.”
qTest Scenario Enterprise is Jira Software add-on for teams practicing behavior-driven development that helps shift testing left and improves alignment between product owners, developers and testers. When integrated with the qTest platform, qTest Scenario Enterprise enables a test-first approach by facilitating BDD test scenario creation, integrated directly into private source code repositories. This ensures feature traceability from Jira directly to the source code, which is integrated into qTest Manager along with all other test results.
Key features of qTest Scenario Enterprise include:
- Jira integration: Testers, developers and product owners can create, update, edit and link feature files using the Jira interface to any issue type. qTest Scenario links test run results in real time to both Jira issues and test results in qTest Manager.
- Simplified script and scenario creation: With qTest Scenario’s autocomplete, BDD teams can better reuse previously implemented Cucumber steps or outlines to streamline feature and scenario creation.
- Source code traceability: qTest Scenario stores all feature files directly in private Git repositories like GitHub and Bitbucket to standardize feature files and scenario steps as code.