Test using QMetry Automation Framework

Introduction

QMetry Automation Framework is designed to solve common industry problems related to testing complex web systems. The framework is best suited for writing Automated Web, Mobile Web, and Mobile Native Application UI Tests simulate real user activities on the page. The framework is built upon java and integrates TestNG, Selenium/Webdriver, Appium, and Perfecto. 

Due to the framework’s thorough design, the test developer does not need to worry about common tasks such as thread-safe browser sessions for running tests in parallel, reporting, or to incorporate results with test management tools. The test run can be configured through standard testing configuration files, the test run filters, and behavior can be changed within the config File.

Here is how you can specify the Test Cases and Test Steps which will be created in QMetry as a part of the result files -

Test Case TagTest Step Tag

Meta-info.json > methods > name

SampleTest.json > Checkpoints > message


Supported file types : ZIP

Sample Test Result File

Meta-info.json

SampleTest.json


Story Association

While importing the test result file, if you want us to link Test Case or Test Scenario to any of the existing stories then it is possible.

An annotation is added to the BDD file to associate scenarios with a particular story in JIRA.

Another option is added to the Java test file to associate scenarios with a particular story in JIRA.

Test Case Reusability

While importing the test result file, if you want us to reuse a Test Case then it is possible.

An annotation is added to the BDD file to reuse test cases in JIRA.



Another option is added to the Java test file to reuse test cases in JIRA.



How Test Case Reusability works if test case key is not provided in BDD file

While importing the test result file, if you want us to reuse a Test Case then it is possible.

  1. If the Test case summary and Test step summary (for all steps) match with the automated Test case name ( Meta-info.json > methods > name) and steps (test_file.json > Checkpoints > message), Test case key and version will be reused.
  2. If Test case summary matches and Test step summary do not match (for any of the steps) with the automated Test case ( Meta-info.json > methods > name), Test case key will be reused but new version will be created.
  3. If Test case summary does not match, the new Test case will be created.

Execution Attachments

To add attachments in test run execution through QAF, enable capturing screenshots in QAS. After that, you will get a folder with all screenshots of automation testing.

You need to provide a zip file containing that output folder of screenshots and JSON output folder.



The relative path of screenshots will be referred from "checkpoints > screenshots" to find the attachment at the relative path in the zip file that is being uploaded.

For example: If the screenshot path is ../img/TC_11.png, then the file name with TC_11.png needs to be available in img folder in the zip file at the root level.