Updating the test case document: Test conditions matrix (TestCondMatrix)

The Test Condition matrix provides a high-level view of the different permutations and combinations of parameters and test data that is used in each test case. Each scenario has its own matrix.

The test condition matrix serves the following purposes:
  1. Facilitates creating unique test cases for each scenario by using different permutations and combinations of parameters and test data.
  2. Shows how many test cases to create by scenario, which maps to how many data sets you have for this scenario.
  3. Ensures that test cases are not repeated with the same test condition.
  4. Ensures that all necessary test conditions for a use case are covered by test cases.
  5. Provides a high-level overview to help reviewers understand the test condition coverage for each test case.

About this task

The TestCondMatrix tab contains the following sections:
Test scenario
A reference cell that contains the name of the scenario from the scenario to use cases mapping tab. Values are automatically populated and no updates are required.
Scenario objective
A reference cell that contains a brief description of the objective referenced from scenario to use case mapping tab. Values are automatically populated and no updates are required.
Test case name
The test case name is a unique identifier that identifies a test case. The test case name is the scenario name with incremental numbers appended. For example, FSTORE.B2C.01-1.
Test condition
A set of different permutations and combinations of parameters or data. Test conditions are logically grouped for easy reference. Conditions are mapped with test cases to meet the following guidelines:
  1. Each condition is covered in at least one test case.
  2. No two test cases cover the same conditions. The left column lists different variables and their possible values for this test scenario. For example, Logon ID is a variable for a registration scenario, it has the values: Valid, Invalid, and Empty.

You can add a test condition matrix, change an existing test condition matrix or remove a test condition matrix.

  • Add

    A test condition matrix is added to the test condition tab if a new test scenario is added in the scenarios to use case mapping tab.

  • Change
    1. A use case is added to an existing test scenario that introduces new test conditions and values
    2. Existing test conditions or values are modified as a result of use case modification
    3. A test case is added to increase test coverage
    4. A use case is removed from an existing Test scenario that removes Test Conditions and Values from the matrix
    5. A use case is modified in an existing Test scenario that removes Test Conditions and Values from the matrix
  • Remove

    A test condition matrix is removed when a test scenario table is removed from the scenarios to use cases mapping tab.

Procedure

  1. Add a test condition matrix
    OptionDescription
    Template test condition matrix exists
    1. Use the existing empty condition matrix. The test case document has two condition matrixes as samples.
    2. For each use case within a Test scenario, identify the Test Conditions and group them in the Test Conditions column.
    3. For each Test Condition, add the possible values under the condition. For example, Logon ID Uniqueness is a condition that has two values – Unique or Duplicate.
    4. For all permutations and combinations to cover in each test case, put an X below the test case Column. Not all combinations are valid, and not all variables are required for every test flow. The author of the FVT test case Document ensures that all correct permutations and combinations are listed.
      1. Map the conditional values to test cases so that each value is tested in at least one test case.
      2. None of the test cases duplicate the same conditional values. Each test case has at least one conditional value that is unique.
    5. Review the Test Condition Matrix to ensure that all combinations of variables make sense for that column.
    Template test condition matrix does not exist
    1. Copy and paste the last Test Condition Matrix to create a matrix.
    2. Update the Test scenario and Test Objective to reference to the corresponding scenario in the scenario to use case Map tab.
    3. Update the first part of test case name formula for each test case in the test case Row For example, CONCATENATE($C$4,"-",$A$1+1) where the first parameter points to the scenario Name. The update is required to point to the respective scenario Name.
    4. Update the Test scenario hyperlink to point to the Test scenario table in the Test scenario to use case Mapping tab.
    5. Creating the Test scenario table following instructions in test case Section; then update the test cases hyperlink to point to the Test scenario Table in the test cases tab.
    6. Delete any sample content.
    7. For each use case within a Test scenario, identify the Test Conditions and group them in the Test Conditions column.
    8. For each Test Condition, add the possible values under the condition. For example, Logon ID Uniqueness is a condition that has two values – Unique or Duplicate.
    9. For all permutations and combinations to cover in each test case, put an X below the test case Column. Not all combinations are valid, and not all variables are required for every test flow. The author of the FVT test case Document ensures that all correct permutations and combinations are listed.
      1. Map the conditional values to test cases so that each value is tested in at least one test case.
      2. None of the test cases duplicate the same conditional values. Each test case has at least one conditional value that is unique.
    10. Review the Test Condition Matrix to ensure that all combinations of variables make sense for that column.
  2. Change an existing test condition matrix.
    OptionDescription
    Add a test condition
    1. Insert new rows at the end of the matrix
    2. For each Test Condition, add the possible values under the condition. For example, Logon ID Uniqueness is a condition that has two values – Unique or Duplicate.
    3. For all permutations and combinations to cover in each test case, put an X below the test case Column. Not all combinations are valid, and not all variables are required for every test flow. The author of the FVT test case Document ensures that all correct permutations and combinations are listed.
      1. Map the conditional values to test cases so that each value is tested in at least one test case.
      2. None of the test cases duplicate the same conditional values. Each test case has at least one conditional value that is unique.
    4. Review the Test Condition Matrix to ensure that all combinations of variables make sense for that column.
    Add a test condition value
    1. Insert a new row under the Test Condition where the value is added
    2. For each Test Condition, add the possible values under the condition. For example, Logon ID Uniqueness is a condition that has two values – Unique or Duplicate.
    3. For all permutations and combinations to cover in each test case, put an X below the test case Column. Not all combinations are valid, and not all variables are required for every test flow. The author of the FVT test case Document ensures that all correct permutations and combinations are listed.
      1. Map the conditional values to test cases so that each value is tested in at least one test case.
      2. None of the test cases duplicate the same conditional values. Each test case has at least one conditional value that is unique.
    4. Review the Test Condition Matrix to ensure that all combinations of variables make sense for that column.
    Remove a test condition
    1. Using the Excel font format strike through, strike out the condition and the values to be removed.
    2. Review the existing test cases to ensure the removal of the condition does not create duplicate test cases.
  3. Remove a test condition matrix
    1. Do not physically remove the test condition matrix from the test condition matrix tab.
    2. Using font format strikethrough option, cross out the content in the matrix to be removed or use the Hide function to hide the rows.