Perform Test Re-Match

After running the test match, based on the new requirements when development teams add new features to the software application, it is important to also test old features. Although existing features have not explicitly changed, new features can have an unintentional impact on older features. By testing the test cases from past releases, testers can ensure that the entire product operates as expected.
tdm35
After running the test match, based on the new requirements when development teams add new features to the software application, it is important to also test old features. Although existing features have not explicitly changed, new features can have an unintentional impact on older features. By testing the test cases from past releases, testers can ensure that the entire product operates as expected.
Testers need to run the test match in multiple iterations to fulfil the test data requirement for the newly added test cases. Datamaker allows you to create a history table, take a snapshot of the test mart and then run a test re-match. This helps the testers to match the newer test cases with right data, retaining the previously allocated reporting keys to older test cases wherever possible.
Refresh Test Mart
As a test data engineer, before each testing cycle, refresh (edit) the test mart to ensure the availability of the current contents of application database(s).
The refreshed test mart contains both the old and new reporting keys. Also the attributes of the old reporting keys can change in the refreshed test mart, due to changes to the respective attributes in the application database(s).
In the new testing cycles, testers add new test cases to TCDC in addition to the old test cases. In such case old test cases are first tried to match with previously allocated reporting keys wherever possible. Where not possible, allocates the old test cases to new reporting keys.
Edit Test Case Data Criteria
Add new test cases as you want to match with the new test data by following the same steps that you followed to edit Test Case Data Criteria for test match. 
Run Test Re-Match
Test re-match considers the old test cases with higher priority compared to new test cases. Test Re-Match is performed in two passes.
In Pass 1, matches the old test cases with previously allocated reporting keys from the snapshot. It uses Priority, Rarity and Order concept for matching. The old test cases are matched fully or partially wherever possible.
In Pass 2, processes the partially matched old test cases and allocates the new reporting keys to the fully matched old test cases. Then processes the new test cases using the Priority, Rarity and Order concept.  If you allow partial matching, retains the partially matched reporting keys for old and new test cases. If you do not allow partial matching, then rolls back the partially matched reporting keys for test cases. Rolled back old test cases are marked with Skipped, and the new test cases for which the data is not available are marked with No Match Found.
Follow these steps:
  1. Right click the test match data pool in which you added the test case data criteria, and then click Test Match.
  2. In the Test Match window, go to Runtime Parameters tab and select Show Advanced Options.
  3. Specify the following and click Match:
    • Limit to a single Test
      Specifies the option to perform test matching on single test case.  This is supported only when you perform test match.
    • Simulate Testmatch
      Select this option to simulate test matching.
    • Allow Partial Matches
      Select to retain the partial matches. If not selected, rolls back the partial matches and marks as Skipped.
    • Retain existing matches where possible
      • Job ID
        Specifies the History Job ID that contains the snapshot of old keys.
      • History Type
        Specifies the type of snapshot.
    • Retry Prior Partial Matches
      Select to re-attempt the test cases which are partially matched in prior runs.
    • No Matching On Clear Down
      Select to clear the existing locks in test mart without performing test matching when used along with Clear Existing Matches checkbox.
    • Snapshot Test Mart before matching
      Select to take snapshot before performing the test re-match.
    • Snaptshot Test Mart after matching
      Select to take snapshot after completing the test re-match.
    • Snapshot Test Mart
      Select to take snapshot of the test mart in the current state without performing the test re-match.
    • Clear Existing Matches
      Select this option to clear existing matches in the test mart before performing test matching
  4. In the Submit Test Match dialog specify the following and click the Go icon.
    • Immediate
      Runs the test match right away.
    • Remote
      Runs the test match as scheduled. Specify the schedule start date, time, email address, and thread in the respective fields. Follow the test data repository time zone.
  5. After successfully completing the test re-match, the view reports dialog opens with the following options:
    • Yes
      Click to open the reports in the browser.
    • No
      Click to exit. To access the reports go to
      %AppData%\Grid-Tools\Testmatch\
      using Run Command.
View Test Re-Match Reports
After successfully running the test re-match, Datamaker provides you the following four types of reports:
  1. Matched Key Report
    This report shows matched keys of both the old and new test cases.
  2. Testmatch Summary Report
    This report shows the summary of test matching for active test cases in Test Case Data Criteria table.
  3. Retain Key Report-PASS1
    This report shows the status of old test cases that are matched with old reporting keys in the snapshot specified. Also shows the data attributes comparison results between old and new reporting keys.
  4. Retain Key Report - PASS2
    This report shows the status of old test cases that are matched with new reporting keys.
  5. JB<id>_RetainKey_Summary - PASS2
    This report shows the test name and match status for pass 2. This report shows the test cases sorted by test name for each test user. The test cases that do not have any test user assigned are displayed first, followed by test cases that are sorted based on the test user name. You can find these reports under the path, ...\AppData\Roaming\Grid-Tools\Testmatch.
  6.  
    JB<id>_RetainKey_<test user name> - PASS2
    This report shows the test name and match status for pass 2 for each test user. A separate report is generated for each test user and placed under the path  ...\AppData\Roaming\Grid-Tools\Testmatch.