In an agile development environment it is very important to integrate your automated and manual testing efforts so you have one combined view of your test coverage. This not only helps with your reporting, but can help in your efforts to Shift Left as manual testers escalate their tests to the automation team, and help validate automation failures by reviewing the corresponding manual tests and log files from the failed test execution.
With that in mind, how do you get all of your legacy automation tests into QMetry Test Manager (QTM)? The video here shows how an automation engineer can quickly import their existing automation test scenarios into QTM as new test cases. We will show you:
- How you can import methods, or actions, as either test cases or test case steps- depending on your preference.
- How QMetry Test Manager intelligently imports methods so they can be used in multiple test scenarios without creating duplicating test cases.
- How QMetry Test Manager imports automated test results and test logs. Lets get started.
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.
First, let’s review our test run config.xml for the parameters of our test. With this file you will see the first test name is “Admin Module Function Test Suite”. The automation script we start out with contains 2 methods that once imported will be test cases in QMetry Test Manager following a successful execution. The sample file actually 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 the first test suite to demonstrate that when we use the same methods multiple times we will not create duplicate test cases.
From QMetry Automation Studio we execute the configuration files using TestNG. We also show the various integration parameters contained within the application properties file allowing you to specify the Domain, Release, Cycle, Platform, Platform Group and build.
Within QAS it’s possible to view the details of the failed test, but the goal of integrating the products is to show how the results can be found in QTM allowing you to take advantage of QTM’s robust reporting engine to review your automation testing inline with your manual testing. This integration also allows testers to review the failed case and open the log files that are typically attached to the test results.
We show a second way to organize and import your test scripts shows how the same methods can be imported as test case steps. Using a different configuration file, Testrun_config2.xml, all of the different scripts will be treated as test cases, the methods as test case steps, and they will be grouped 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 also update those test cases. To demonstrate this I will move sampleTestMethodB from Test Case 2 to Test Case 1 and re-run the automation test. After the execution the test cases will be updated with a new version. And the test suite will show updated results with the correct version of the test case that was executed along with the Executed Build (the build is optional, but is highly recommended to help you record test results across builds helping you spot common regressions / automation failures).
I hope the video helps to show you how to get started integrating your automation tools with QTM.