Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Supported file types : XML

Sample Test Result File

Click here to download the Sample Test Result File. 

...

Reuse Manual Test Cases

Keyword

Download Sample File

Description

testcasekey

View file
nameTestNg_multipleTest.xml

  • When a valid test case key is passed through the result XML file and the executed test steps match with the steps and summary of any version of the existing test case key, then the existing test case version will be reused.

  • When a valid test case key is passed through the result XML file and the executed test steps do not match with the steps of any version of the existing test case key, then a new version of the test case will be created and will be used on the execution screen.

  • When an invalid/archived test case key is passed through the result XML file:

    • If the executed test steps match the steps and summary of any version of the existing test case, then the existing test case version will be reused.

    • If the executed test steps do not match the steps and summary of any version of the existing test case, then a new test case will be created.

  • If a manual test case includes the manual steps, which are the same as test methods (using a shareable test case), then on uploading the test result using API, a new version will be created

    While importing test result file, if you want to reuse test cases, then it is possible.

    The mapping of test steps depends on the matchTestSteps parameter.

    If the matchTestSteps parameter is set as “True” (Default): Create/Reuse a test case with a summary and test steps that exactly match the automated test case uploaded through the result file. The execution results and other execution details of the test case and steps will be imported from the automation result file.

    • If Test Case Summary and Test Step Summary (for all steps) match with the automated Test Case Name ( elements > name) and steps (elements > steps > name), Test Case Key and version will be reused.

      • If Test Case Summary matches with the automated Test Case ( elements > name) but Test Step Summary does not match (for any of the steps), Test Case Key will be reused but a new version will be created.

      • If Test Case Summary does not match, a new test case will be created.

    If the matchTestSteps parameter is set as “False”:

    When the Test Cycle is not been Reused

    → Create/Reuse a test case with a summary or test case key that exactly matches the automated test case uploaded through the result file, and exclude matching of test steps. The execution results of the test case will be imported or calculated based on the test case/step results from the automation result file. The execution result of the test case will be propagated to the test steps in the case of test case reuse/creation. Individual test case steps will not be matched and their execution results/details will not be picked from the result file.

    When the Test Cycle is been Reused

    When the Test Case Key is mapped in the result file and the Test Case Key is found linked to the Test Cycle.

    The existing linked test case version, which is part of the Test Cycle will be used. If multiple versions of the same test case key are linked to the test cycle, the one which traced first will be used. The test steps will not be matched to create a new version or link a different version.

    → When the Test Case Key is mapped in the result file and the Test Case Key is not linked to the Test Cycle and the Test Case Key exists in the Test Case Library.

    The existing latest version of the test case that matches based on the test case summary will be linked to the existing Test Cycle. If there are multiple test cases with the same summary exist, the one which is traced first will be linked to the existing Test Cycle. The test steps will not be matched to create a new version or link a different version.

    → When the Test Case Key is mapped in the result file and the Test Case Key is not found linked to the Test Cycle and the Test Case Key is not found in the Test Case Library, and the Test Case Summary matches with any existing test cases linked to the Test Cycle.

    The existing linked Test Case version which is part of the Test Cycle will be used. The test steps will not be matched to create a new version.

    → The Test Case Key is not mentioned in the result file and the Test Case Summary matches any existing test case that is already linked to the Test Cycle.

    The existing linked Test Case version which is part of the Test Cycle will be used based on the summary. The test steps will not be matched to create a new version.

    → When the Test Case Key is mapped in the result file and the Test Case Key does not exist in the Test Cycle OR is Not found in Library and the Test Case Summary also does not match any existing Test case in the Test Cycle andTest Case with the same summary isfound in the Test Case Library.

    The existing latest version of the test case that matches based on the test case summary will be linked to the existing Test Cycle. If there are multiple test cases with the same summary exist, the one which is traced first will be linked to the existing Test Cycle. The test steps will not be matched to create a new version or link a different version.

    → When the Test Case Key is mapped in the result file and the Test Case Key does not exist in the Test Cycle OR is Not found in Library and the Test Case Summary also does not match any existing Test case in the Test Cycle OR is not found in the Test Case Library.

    A new test case without steps will be created and will be linked to the Test Cycle being reused.

    The execution results of the test case will be imported or calculated based on the test case/step results from the automation result file. The execution result of the test case will be propagated to the test steps in the case of test case reuse/creation. Individual test case steps will not be matched and their execution results/details will not be picked from the result file.

    In a project where propagation is off, the status of the step will not be mapped or changed.

    • Multiple test case keys (i.e. testcasekey) can be linked with a single test suite, which will update/create multiple test cases and link these test cases with an automated test suite. Multiple test case keys can be passed in the same tag e.g.

    <group name="testcasekey:FIT-TC-1 FIT-TC-2 FIT-TC-3">

    • When Group(s) are defined at Suite level followed by a Test(s): If the Group's Class Name matches with the Test's Class Name, the Test Case Key/Story will be linked with those Tests.

    ...