IEEE 829-1998, also known as the 829 Standard for Software Test Documentation, is an IEEE standard that specifies the form of a set of documents for use in eight defined stages of software testing, each stage potentially producing its own separate type of document. The standard specifies the format of these documents but does not stipulate whether they all must be produced, nor does it include any criteria regarding adequate content for these documents. These are a matter of judgment outside the purview of the standard. The documents are:
* Test Plan: a management planning document that shows:
* How the testing will be done (including SUT (system under test) configurations).
* Who will do...

What is test plan in software testing?Software testing is a planned, organized and systematic software quality assurance steps, rather than casual, loosely and messy implementation of QA activities.
As per IEEE Standard 829-1982 definition a software test plan is a document which describes the scope of the testing activities, approach, resources, schedule, test features, test tasks and any risk associated with the testing. Test planning in software testing helps the QA members, especially test manager to have a clear mission and testing methods to maintain smooth communication and progress tracking during various testing phases.

A good software test plan is not an easy thing...

1. What is a IEE Standard 829 Sample Test Plan Template:

Sections for inclusion:

Test Plan identifier: A unique name or number, useful if you store all documents in a database.
Introduction:  Include references to all relevant policy and standards documents, and high-level product plans.
Test items: A test item is a software item (function, module, feature, etc) that is to be tested. List them all, or refer to a document that lists them all. Include references to specifications (e.g. requirements and design) and manuals.
Features to be tested: Cross-reference them to test design specifications.
Features not to be tested: Which ones and why not.
Approach: Describe the overall...

Complete Tutorial on Test Plan

For reference purposes, the sections that the IEEE 829–1998 standard recommends have been listed below:


Test Plan Identifier

Each test plan and, more importantly, each version of a test plan should be assigned an identifier that is unique within the organization. Assuming the organization already has a documentation configuration management process (manual or automated) in place, the method for determining the ID should already have been determined. If such a process has yet to be implemented, then it may pay to spend a little time trying to improve this situation before generating additional documentation

Introduction

Given that test-planning...

The success of testing activity generally depends on how well you plan for it. This article provides a few guidelines based on which you can plan your testing activity better. Remember the article is only a guideline to your planning process. You have to innovate and develop your own plan based on the application you are working on.


Build the Plan



1. Analyze the product.



What to Analyze



· Users (who they are and what they do)

· Operations (what it’s used for)

· Product Structure (code, files, etc.)

· Product Functions (what it does)

· Product Data (input, output, states, etc.)

· Platforms (external hardware and software)



Ways to Analyze...