Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

Test Case TagTest Step Tag
Scenario > nameStatement with Given, When, Then keyword 


QMetry uses following tags of QAF output result file to create Test cases and Steps.

Test Case TagTest Step Tag

Meta-info.json > metaData> methods > name

checkPoints > message


Supported file types : ZIP

The following feature file is showing syntax for story association and test case reusability.



Sample Test Result File

Click to download a Sample Test Result File: Feature json sample.zip


Meta-info.json

Image Modified


Test Case Reusability and Story Association

...

Expand

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 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.

Image RemovedImage Added



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

Image RemovedImage Added


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.

...