Updating the test case document: ScenarioUsecaseMap

Scenarios to Use Cases mapping table provides a list of Use Cases that are covered by each Test Scenario. This is a reverse mapping of the previous Use Case to Scenario mapping. The Use Cases in these Test Scenario tables are referenced from Use Case to Scenario mapping. The Additional Document Links provide relevant information for each use case that can be used as reference material.

There is one table for each scenario. From each scenario, the test case and test condition matrix section can be browsed to by clicking the links provided.

Scenario name
The scenario name is a logical name which identifies a scenario. The scenario name follows this naming convention:
  • The first letter stands for the type of test.
    F
    FVT
    S
    SVT
  • Followed by an abbreviation of the project code name. For example, Store for scenarios that are developed as part of store front development.
  • Followed by a . and the store type (B2C or B2B)
  • Followed by a unique two-digit scenario numbers. Numbering begins with 01.
Your naming convention might be different.
Scenario objective
Provides a brief high-level description of the scenario.
Use cases
Lists the Use Cases that are involved in the scenario. These Use Cases are referenced from Use Case to Scenarios mapping.
Additional documents link
Provides links to the WebSphere Commerce Version 7 documentation when applicable. For new Use Cases, add reference links if available.

About this task

Test Scenario table is updated after you complete the updates to the Use Case to Scenarios mapping matrix. Follow the instructions to update the Test Scenario Tables in the Scenario to Use Case mapping tab.

A new Test Scenario can be added to the Test Case Document for the following reasons:
  1. A new Use Case is added
  2. Test coverage is added to minimize the risk in the test plan and increase the coverage in sensitive or risky areas specific to your project.
  3. An existing Use Case is modified.

Procedure

  1. A template Test Scenario table exists:
    1. Use the blank Test Scenario table and complete the details of the new Test Scenario. One sample Test Scenario table is provided at the end of the Scenario to Use Cases mapping tab.
    2. Update the Test Scenario Objective
    3. Refer to the mappings (X) under the Scenario column in the previous Use Case to Scenarios mapping tab to identify the Use Cases that are involved in each Test Scenario.
    4. Update the Use Cases column by referencing the applicable Use Cases from the Use Cases to Scenario mapping tab.
    5. Update the Additional Information Link if you have your own information development documents for the added use case. If you do not have new information development documents, this portion can be left blank.
  2. A template Test Scenario table does not exist:
    1. Copy and paste the last Test Scenario table at the end of the Scenarios to Use Cases Mapping tab
    2. Update the Scenario Number in the table header.
    3. Update the Scenario Name that uniquely identifies the Test Scenario
    4. Update the link to the Condition Matrix after you create the Condition Matrix in the Condition Matrix tab by following the instructions in Test Condition Matrix Section
    5. Update the Test Cases Link after you create the Test Scenario Table in the Test Cases tab by following the instructions in Test Cases Section
    6. Use the blank Test Scenario table and complete the details of the new Test Scenario. One sample Test Scenario table is provided at the end of the Scenario to Use Cases mapping tab.
    7. Update the Test Scenario Objective
    8. Refer to the mappings (X) under the Scenario column in the previous Use Case to Scenarios mapping tab to identify the Use Cases that are involved in each Test Scenario.
    9. Update the Use Cases column by referencing the applicable Use Cases from the Use Cases to Scenario mapping tab.
    10. Update the Additional Information Link if you have your own information development documents for the added use case. If you do not have new information development documents, this portion can be left blank.