Prev | Current Page 299 | Next

Peter Farrell-Vinay

"Manage Software Testing"


???
Service level:
Non-functional requirements to be met by the services provided by the interface
(operations) and covers guarantees regarding any quality or non-functional requirement or constraint
to be met by the interface and its operations.
???
Notes:
Limitations on use, pre-requisites, references, standards, and diagrams.
???
Layers:
In the event that the interface is layered, the above-listed sections will be repeated for each
layer. Describe the relations between the layers.
8.5 Test Plan
The test activities foreseen throughout a project for each particular type of testing are described and
coordinated in a test plan. A test plan defines the purpose, scope, approach, resources, and responsibilities
of the testing activities. It will also identify each item to be tested, the testing tasks to be performed and
the risks associated with each item and activity.
Typical objectives for a test plan are:
??? To detail the activities required to ensure the testing is effective,
??? To define the test tools and test environment needed to conduct the test,
??? To determine the schedule of activities.
The contents of a test plan are:
???
Introduction:
Summarize items and features to be tested.
???
Items to be tested:
List them with version numbers and transmission media.
???
Features/features to be tested/not to be tested:
List them with reasons, and references to the
relevant specification, together with a feature/test matrix.


Pages:
287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311