A
summary of test cases that are
documented in the Functional Verification Test Case
document.
TestOverview contains
the following sections:
- PurposeSummarizes
test cases that are documented in the Functional Verification Test
Case Document.
- AssumptionsLists
detailed assumptions that are made for the test cases and test execution
that are not listed in the High Level Functional Verification Test
Plan. The assumptions that are listed can be assumptions that are
specific to the test cases, assumptions that the person who is running
the test cases must know, or assumptions that are made after the High
Level Functional Verification Test Plan is approved.
- Test
ConfigurationDescribes the overall environment
where the FVT test cases are run. It details the client side requirements
(browsers, operating systems, and specific tools) and a brief description
of the overall server environment. This is just a summary as the
details of these environments exist in the High Level Functional Verification
Test Plan. For instance, the type of information that is stated is
the type of operating system, database, and stubs or simulators that
are used for testing.
- ExclusionsLists
the detailed exclusions that are not already listed in the High Level
Functional Verification Test Plan. The exclusions that are listed
can be exclusions that are specific to the test cases, exclusions
that the person who running the test cases must know or exclusions
that are made after the High Level Functional Verification Test Plan
is approved.
Procedure
- Update
the Purpose section.
What to update: Purpose should
match your project’s FVT purpose
and align with the High Level Functional Verification Test Plan document.
- Update the Assumptions section.
What to update: - Understand
the assumptions that are already listed in the starter
store test case document that is delivered and validate whether they
are still applicable.
- Add or modify the test assumptions and
have the stake holders
agree before testing begins.
- If there are no assumptions that
made, explicitly mention that
there is no new assumption made.
- Update the Test
Configuration section.
What to update: - Update to include what is agreed upon in the
High Level Functional
Verification Test Plan. The update can be a quick summary, a reference
to the High Level Functional Verification Test Plan, or both.
- For
the client side configurations, provide a list of which test
cases are run on which configuration.
For
example: Indicate the test case
to be run on which browser and which operating system.
- Update the Exclusions section.
What to update: - Explain
the risks that are involved in excluding any test areas.
Understand the exclusions that are already listed in the starter store
test case document that is delivered and validate whether they are
still applicable. Add test coverage if you do not want to take risks
in the areas that are excluded in the starter store test case document.
If
you are planning to change the test coverage in the starter store
test case document to exclude more areas, the information must be
documented.
- Update the exclusions that the person using the
Functional Verification
Test Case Document must know.
- Explicitly mention if there
is nothing that is excluded.
For example: Scenario
10 is excluded
from execution on Safari browser because Organization Admin Console
cannot be accessed using Safari browser.