hello,
I am aware of the step called testing in the process
of software development.
But what do you mean by a term callled Test-Plan ?
Please provide your ideas regarding this....
thank you....
Printable View
hello,
I am aware of the step called testing in the process
of software development.
But what do you mean by a term callled Test-Plan ?
Please provide your ideas regarding this....
thank you....
A test plan documents the strategy that will be used to verify and
ensure that a product or system meets its design specifications and
other requirements.
A test plan is usually prepared by or with significant input
from Test Engineers.
Depending on the product and the responsibility of the organization to which the test plan applies, a test plan may include one or more of the following:
Design Verification or Compliance test - to be performed during the development or approval stages of the product, typically on a small sample of units.
Manufacturing or Production test - to be performed during preparation or assembly of the product in an ongoing manner for purposes of performance verification and quality control.
Acceptance or Commissioning test - to be performed at the time of delivery or installation of the product.
Service and Repair test - to be performed as required over the service life of the product.
Regression test - to be performed on an existing operational product, to verify that existing functionality didn't get broken when other aspects of the environment are changed (e.g., upgrading the platform on which an existing application runs).
In the simplest form - A test plan is a systematic approach to testing a system such as a machine or software. The plan typically contains a detailed understanding of what the eventual workflow will be.
Early in the deployment planning phase, the testing team creates a test plan.
The test plan defines the objectives and scope of the testing effort, and identifies the methodology that your team will use to conduct tests.
-It also identifies the hardware, software, and tools required for testing and the features and functions that will be tested.
-A well-rounded test plan notes any risk factors that jeopardize testing and includes a testing schedule.
If your testing team is divided into technology subteams, each subteam should develop a test plan for that team’s specific technology area.
For example, the networking team would write a test plan for testing networking features. All members of each subteam should review and
approve its team’s test plan before it is integrated into the general test plan.
Here, I will show you how to create a test plan graphically -