to In an agile development environment it is very important to integrate your automated testing and manual testing efforts. Along with your reporting it can help in your efforts to Shift Left. Manual testers escalate their tests to automated testing team, and help validate automation failures by reviewing corresponding manual tests and log files from the failed test execution.
So, how do you get all of your legacy automation tests into QMetry Test Management (QTM)? The video here shows how an automation engineer can quickly import existing automated test scenarios into QTM as new test cases.
- See how you can import methods, or actions, as either test cases or test case steps
- Know how QMetry Test Management intelligently imports methods so they can be used in multiple test scenarios without creating duplicating test cases.
- How QMetry Test Management imports automated testing results and test logs. Let’s start.
We use QMetry Automation Studio (QAS); however, the familiar Eclipse based IDE interface shows how any tool can be used to import the test scripts into QTM through the API.
let’s review our test run config.xml for the parameters of our test. You’ll see the first test name is “Admin Module Function Test Suite”. The automation script contains 2 methods that once imported will be test cases in QMetry Test Management. Sample file contains two test suites, the second being “Delete Project, User Role and User Functionality Test Suite”. This second test suite contains two of the same scripts used in first test suite to demonstrate that the same methods when used multiple times will not create duplicate test cases.
From QMetry Automation Studio execute the configuration files using TestNG. We show the various integration parameters contained within the application properties file. We allow you to specify the Domain, Release, Cycle, Platform, Platform Group and build.
Why Integration of Products?
Within QAS it’s possible to view the details of the failed test. The goal of integrating the products is to allow you to take advantage of QTMs robust reporting engine to review your automated testing inline with your manual testing. This integration also allows testers to review the failed case. Also opens the log files that typically attach to the test results.
How to Organize and Import Test Scripts?
We show a second way to organize and import your test scripts. Testrun_config2.xml, a different configuration file, treats all of the different scripts as test cases and the methods as test case steps. Also, groups them as one test suite called Demo Test Suite.
Once launched the automation run will start creating the new assets in QTM. In addition to importing test cases we can update those test cases. I will move sample Test MethodB from Test Case 2 to Test Case 1 and re-run the automation test. After the execution the test cases update with a new version. Results for the test suite are shown with the correct version of the test case executed along with the Executed Build (the build is optional, but it’ll help you record test results across builds to help you spot common regressions / automation failures).
I hope the video helps to show you how to start integrating your automation tools with QTM.