Test stage: Functional test plan and test case document
WebSphere Commerce provides a set of test assets to help you plan and run the functional verification testing for the starter store.
Click the tabs to find modifiable documentation templates that you can use to accelerate project progress and reduce the costs of a WebSphere Commerce project.
| Concept stage | Design stage | Implementation stage | Testing stage | Launch stage | Maintenance stage |
 |
|||||
Introduction
You can use the test assets that are provided with WebSphere Commerce as a starting point to further develop the test plan.
The following test store assets are
provided:
- Use case document
- Contains the use cases that are supported by the store.
- High level functional verification test plan
- A document, written at the beginning of the test cycle, between the development team, project management team, and the Functional Verification Testing (FVT) team. The plan describes test coverage and scope that is used to test the use cases that are described in the Use case document. The plan is reviewed and approved by the stakeholders before the beginning of FVT execution.
- Functional verification test case document
- Detailed test procedures to test the features that are provided in your store as specified in the use cases in the Use case document.
- How to document
- Describes how to read, understand, and update the High Level Functional Verification Test Plan and Functional Verification Test Case Document.
- Automation Framework and test scripts
- An automation package is provided with the automation framework and test scripts. Automated test scripts can be used to validate existing functionality and extend to new test cases.
Best practices
- Have a requirements gathering meeting with stake holders before planning the functional verification test
- Once the requirements are understood, have a planning meeting
with the stake holders, product owner, project management, and team
members agree on:
- What to test
- When to test
- How to test
- Using the High Level Functional Verification Test Plan template as a starting point, complete the high-level test plan and review the document before starting to test. Do not start detailed test cases until the high-level plan is reviewed.
- The Functional Verification Test Case document must be updated and reviewed before the test execution begins.
- Existing automated test scripts can be used to test unchanged features. For new test cases, the existing automation tasks can be used.
- To maximize the test coverage, the person who writes the code unit tests, but does not perform functional test
- It is inefficient to test every possibility in a functional verification test. Testers must understand the high probability and high risk scenarios and test more on that area.
Download
Download the Store Front Test Automation
Engine that corresponds to your feature pack:
See 
