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
.
- The first
letter stands for the type of test.
- 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:
- A new Use Case is added
- 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.
- An existing Use Case is modified.