Page Comparison

1

Testsuite, Test Case, Test Step

Testsuite will be created based on testsuiteName parameter in Automation API or Auto generated if not mentioned.

<testsuite> tag  : Parsed from the result file.

Junit File Type 1: Wherein testsuite "name" matches the test case "classname".

• Test Suite will have test cases as per the <testsuite> tag with steps as per the <testcase> tags.

• Only one version of test cases will be created with multiple test steps.

<testsuite> tag : Parsed from the result file.

Junit File Type 2: Wherein testsuite "name" does not match the test case "classname".

• Test Suite will have multiple versions of the same test case linked as per the <testsuite> tag.

• The number of versions will match the occurrences of the <testcase> tag.

• For each test case version, there will be one test step.

<testcase> tag under the <testsuite> tag  : Parsed from the result file.

Classname.name will be the Test Step Description.

If the result file does not have a classname tag, the Test Step Description will begin without a dot (.)e.g., name.

Execution Status in QMetry will be determined based on the result mentioned in the result file as shown below.

Tag inside <testcase>

<failure>

Failed

no tags

Passed

<error>

If the Aborted status is found in the JUnit result file either by referring to the Status or Error Tag

QMetry will set the Test Case Execution Status or Step Execution Status as

If the Project have the custom execution status “Aborted”

Aborted

If the Project does not have the custom execution status “Aborted”

Failed

<skipped>

If the Skipped status is found in the JUnit result file by referring to the Status

QMetry will set the Test Case Execution Status or Step Execution Status as

If the Project have the custom execution status “Skipped”

Skipped

If the Project does not have the custom execution status “Skipped”

Not Applicable

2

Testsuite, Test Case

Testsuite will be created based on testsuiteName parameter in Automation API or Auto generated if not mentioned.

<testcase> tag under the <testsuite> tag : Parsed from the result file.

classname.name will be the Test Case summary.

If the result file does not have a classname tag, the Test Step Description Case Summary will begin without a dot (.)e.g., name.

NA

Tag inside <testcase>

Execution Status in QMetry

<failure>

Failed

no tags

Passed

<error>

If the Aborted status is found in the JUnit result file either by referring to the Status or Error Tag

QMetry will set the Test Case Execution Status or Step Execution Status as

If the Project have the custom execution status “Aborted”

Aborted

If the Project does not have the custom execution status “Aborted”

Failed

<skipped>

If the Skipped status is found in the JUnit result file by referring to the Status

QMetry will set the Test Case Execution Status or Step Execution Status as

If the Project have the custom execution status “Skipped”

Skipped

If the Project does not have the custom execution status “Skipped”

Not Applicable

3

Testsuite, Test Case

<testsuite> tag 

<testcase> tag under the <testsuite> tag : Parsed from the result file.

classname.name will be the Test Case summary.

If the result file does not have a classname tag, the Test Step Description Case Summary will begin without a dot (.)e.g., name.

NA

Tag inside <testcase>

Execution Status in QMetry

<failure>

Failed

no tags

Passed

<error>

If the Aborted status is found in the JUnit result file either by referring to the Status or Error Tag

QMetry will set the Test Case Execution Status or Step Execution Status as

If the Project have the custom execution status “Aborted”

Aborted

If the Project does not have the custom execution status “Aborted”

Failed

<skipped>

If the Skipped status is found in the JUnit result file by referring to the Status

QMetry will set the Test Case Execution Status or Step Execution Status as

If the Project have the custom execution status “Skipped”

Skipped

If the Project does not have the custom execution status “Skipped”

Not Applicable