A test plan is a systematic approach to testing a system such as a machine or software. A machine is any device that uses Energy to perform some activity The plan typically contains a detailed understanding of what the eventual workflow will be. A workflow is a depiction of a sequence of operations declared as work of a person work of a simple or complex mechanism work of a group of persons work of an organization of staff
Contents |
Criticism of the overuse of test plans
Cem Kaner, co-author of Testing Computer Software (ISBN 0-471-35846-0), has suggested that test plans are written for two very different purposes. Sometimes the test plan is a product; sometimes it's a tool. It's too easy, but also too expensive, to confuse these goals. In other words, a test plan is like a power tool. You should not utilize them if you don't know what you're doing with them. You are wasting both time and money.
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. 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
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). Design for Test (aka "Design for Testability" or "DFT" is a name for design techniques that add certain testability features to a microelectronic
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) Test items;
- d) Features to be tested;
- e) Features not to be tested;
- f) Approach;
- 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. The Institute of Electrical and Electronics Engineers or IEEE (read eye-triple-e) is an international Non-profit, professional organization
See also
- Software testing
- Test suite
- Test case
- Test script
- Scenario testing
- Session-based testing
- IEEE_829
- Test engineer
External links
- Zephyr Test Plan Management Software
- Public domain RUP test plan template at Sourceforge
- Test plans and test cases from the Applied Software Project Management website (O'Reilly)
- What is a Test Plan?
Dapyx Software network: MP3 Explorer | Ebook Manager | Zenithic