Test plan


Test plan

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.

Test plans in hardware development

A test plan documents the strategy that will be used to verify and ensure that a hardware 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. A complex system may have a high level test plan to address the overall requirements and supporting test plans to address the design details of subsystems and components.

Test plan document formats can be as varied as the products and organizations to which they apply, but there are three major elements of a test strategy that should be described in the test plan: Test Coverage, Test Methods, and Test Responsibilities.

Test coverage in the test plan states what requirements will be verified during what stages of the product life. Test Coverage is derived from design specifications and other requirements, such as safety standards or regulatory codes, where each requirement or specification of the design ideally will have one or more corresponding means of verification. Test coverage for different product life stages may overlap, but will not necessarily be exactly the same for all stages. For example, some requirements may be verified during Design Verification test, but not repeated during Acceptance test. Test coverage also feeds back into the design process, since the product may have to be designed to allow test access (see Design For Test).

Test methods in the test plan state how test coverage will be implemented. Test methods may be determined by standards, regulatory agencies, or contractual agreement, or may have to be created new. Test methods also specify test equipment to be used in the performance of the tests and establish pass/fail criteria. Test methods used to verify hardware design requirements can range from very simple steps, such as visual inspection, to elaborate test procedures that are documented separately as Test Cases under various Test Scenarios.

Test responsibilities include what organizations will perform the test methods and at each stage of the product life. This allows test organizations to plan, acquire or develop test equipment and other resources necessary to implement the test methods for which they are responsible. Test responsibilities also includes, what data will be collected, and how that data will be stored and reported (often referred to as "deliverables"). One outcome of a successful test plan should be a record or report of the verification of all design specifications and requirements as agreed upon by all parties.

IEEE 829-1998:

:a) Test plan identifier;:b) Introduction;:c) Approach;:d) Test items;:e) Features to be tested;:f) Features not to be tested;:g) Item pass/fail criteria;:h) Suspension criteria and resumption requirements;:i) Test deliverables;:j) Testing tasks;:k) Environmental needs;:l) Responsibilities;:m) Staffing and training needs;:n) Schedule;:o) Risks and contingencies;:p) Approvals.

ee also

*Software testing
*Test suite
*Test case
*Test script
*Scenario testing
*Session-based testing
*IEEE 829
*Test engineer

External links

*Public domain RUP test plan template at [http://jdbv.sourceforge.net/RUP.html Sourceforge] (templates are currently inaccessible but sample documents can be seen here: [http://jdbv.sourceforge.net/Documentation.html DBV Samples] )
* [http://www.stellman-greene.com/testplan Test plans and test cases] from the [http://www.stellman-greene.com/aspm Applied Software Project Management] website (O'Reilly)
* [http://testingsoftware.blogspot.com/2005/11/what-is-test-plan_30.html What is a Test Plan?]


Wikimedia Foundation. 2010.

Look at other dictionaries:

  • План тестирования/TEST PLAN — план и процедуры, используемые для испытания жизнеспособности системы и предусматривающие осуществление мероприятий, которые будут выполнены в случае реального бедствия …   Толковый словарь по информационному обществу и новой экономике

  • Test pilot — Test pilots are aviators who fly new and modified aircraft in specific maneuvers, allowing the results to be measured and the design to be evaluated. Test pilots may work for military organizations or private, (mostly aerospace) companies.… …   Wikipedia

  • Test management — is the activity of managing some tests. A test management tool is a Software used by Quality Assurance team to manage the tests (automatic or not) that have been previously specified. It is often associated with an Automation software. Test… …   Wikipedia

  • Test data — are data which have been specifically identified for use in executing test scripts, and are used to verify the expected results obtained.ee also*Software testing *Unit test *Test plan *Test suite *Scenario test *Session based test References *… …   Wikipedia

  • Test engineer — A (hardware) test engineer (TE) is a professional who determines how to create a process that would test a particular product in manufacturing, or related area like RMA department, in order to guarantee that the product will be shipped out with… …   Wikipedia

  • Test case — A test case in software engineering is a set of conditions or variables under which a tester will determine if a requirement or use case upon an application is partially or fully satisfied. It may take many test cases to determine that a… …   Wikipedia

  • Test suite — In software development, a test suite, less commonly known as a validation suite , is a collection of test cases that are intended to be used to test a software program to show that it has some specified set of behaviours. A test suite often… …   Wikipedia

  • Test script — A test script in Software Testing is a set of instructions that will be performed on the System Under Test to test that the system functions as expected. These steps can be executed manually or automatically.There are various means for executing… …   Wikipedia

  • Plan de crise pour une pandemie — Plan de crise pour une pandémie Dans un contexte de mondialisation et de risque accru de diffusion de maladies émergentes, la définition d un plan de crise pour une pandémie est devenu une préoccupation partagée pour de nombreux acteurs… …   Wikipédia en Français

  • Test de Charge — Test de performance Un test de performance ou benchmark est un test dont l objectif est de déterminer la performance d un système informatique. L acception la plus courante de ce terme est celle dans laquelle ces tests logiciels vont avoir pour… …   Wikipédia en Français


Share the article and excerpts

Direct link
Do a right-click on the link above
and select “Copy Link”

We are using cookies for the best presentation of our site. Continuing to use this site, you agree with this.