Test management platforms give Agile teams a suite of software testing tools designed to improve speed, efficiency, and collaboration throughout the software testing life cycle. Requirements, test cases, and defects can all be captured and managed to foster better results. By now, most teams have standardized on their platform of choice and have invested time and resources into their chosen platform.
That is not always the case with test automation. For those that haven’t standardized on their test automation software, you would be wise to check out Apexon’s Quality Automation Framework QAF. This is our open-source test automation framework, built based on thousands of hours of test automation experience. It has powerful features for writing robust automation and delivering better testing ROI by reducing maintenance, development, and execution costs. It also provides out-of-the-box integration with tools like ALM, qTest, QTM, Perfecto by Perforce, Sauce Labs, and Jenkins, and is easy to scale with cloud technologies.
In this post, we will walk you through QAF’s integrations with test management platforms.
Developer APIs to Access Platform
Apexon has leveraged the respective test management platform APIs and integrated the QAF framework seamlessly with test management platforms to publish automation execution results directly into the respective platform. This one-way integration means that once the automation execution is completed, the result will be pushed to the test management platform, updating the test case with steps status, including logs and screenshots for further analysis.
Integration with qTest Tricentis Platform
Let’s take the qTest platform as an example.
qTest is a popular test management tool from Tricentis. The Apexon team has built an accelerator to update test automation results into qTest. Some high-level features provided by this accelerator for seamless integration between automation code and qTest platform are:
- Auto-create test case in qTest if it doesn’t exist.
- Auto create test-cycle/test-suite if it doesn’t exist.
- Update test case status
- Attach success/failure screenshot
- Update QAF BDD steps in test
- Configurable properties
To integrate your automation code with qTest, the user just needs to add the required dependencies into the codebase. Below is an example for a Maven project.
After adding dependencies to the project, you need to set a few more properties in the application.properties file to provide details for qTest instances.
Now the integration is ready, the user can map the test case with qTest test instances by using the QAF framework annotation called @MetaData.
So, now when you execute the script above, the automated test will automatically update the result for the test with the ID “TC01” into the qTest release cycle along with status, logs and screenshot (by default only if it has failed).
Other Platforms (ALM, QTM…)
Similar to the above qTest integration, QAF does support other test management platforms like ALM, QTM and others. The same configurations need to be provided for the respective platforms. You can check out QAF integrations documentation for more details.
Key benefits of QAF integration:
- QAF abstracts the implementation of the integration of a particular platform and provides an easy way to map your manual test cases with automated ones.
- It supports both TDD and BDD approaches.
- Integration related configuration is outside of the actual automation code, and depending upon your needs, you just need to adjust settings in Properties. No coding is required.
- Support test as well as step level integration support for most test management platforms.
- Screenshot capturing feature at success and failure level.
- The automation execution logs are automatically attached to the manual test case. This helps manual QA to analyze the issue further.
If you’d like more information about QAF & test management platform integration, complete the form below.
