TESTINGMANTRA - BLOG
Blog
Testing Types
Usability Testing
Smoke Testing
Load Testing
Stress Testing
Domain Testing
Exploratory Testing
Recovery Testing
Scenario Testing
Regression Testing
User Acceptance Testing
Alpha Testing
Beta Testing
Unit Testing
Static & Dynamic Analysis Testing
Functional Testing
Ad-hoc Testing
Volume Testing
System Testing
Sanity Testing
Black Box Testing
Interoperability Testing
Volume Testing Techniques
Gray Box Testing
White Box testing
Articals
Agile Development
Coverage Criteria for GUI Testing
Release Life Cycle
Quality Concept
TQM - Total Quality Management
When are the Test Plan written
Unit Testing Advantages & Techniques
Classification of Defect
Requirement Testing Techniques
When is Testing Complete?
Quantative Project Management
Software Configuration Management
When to use Regression Testing?
V-Model Concept of Testing
Activity of Software Test Engineer
Risk Management
Sanity Testing A Overview
Website Security Smoke Test Template
Software Testing Techniques
Requirements & Specifications
Traceability Matrix
Test Plan - Objectives and Benefits
Agile Testing - Master the new game
Testing Vocabulary
SQL Tutorial
Test Strategy
Error Handling Testing
SDLC - Concept
Steps of Software Testing Life Cycle
Why to use Metrics?
Defect Tracking
SyncML
Mobile Testing
GSM Basic
Cellular Network Architecture
Mobile Communication Overview
Mobile & handheld usability testing
Why Mobile Testing is different
True BREW Testing
VOIP Testing
SIP Testing - An overview
SIP Messages
Structure of SIP Protocol
SIP Important terms
SDLC Model
Software Development Life Cycle
Waterfall model
Spiral Model
V-Model
Iterative Model
Big Bang Model
RAD Model
Prototype Model
SOFTWARE TESTING
Test Plan
Test Case & Test Design techniques
Templates
Software Project Template
Software Testing Template
Automated Testing Tools
QTP
Winrunner
JUnit
Selenium IDE
LoadRunner
JMeter
Estimation Techniques
Using Use Case Points
Quick Estimation Technique
Testing Estimation Process
Certifications
CSQA
CSTE
                                                                                                                                                                  Usability Testing      Smoke Testing      Load Testing      Stress Testing      Domain Testing      Exploratort Testing       Recovery Testing      Scenario Testing      Regression Testing      User Acceptance Testing      Alpha Testing      Beta Testing      Unit Testing      Static & Dynamic Analysis Testing                                                                                             







Share
Follow us at Twitter
Follow us at Facebook
Share
What  is a Test Plan:
The ANSI/IEEE Standard defines a Test Plan as -
A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning. Test plan is created by test lead or test manager. Test plan is used to keep track of each steps of activities in testing. If we follow the test plan, a quality product can be deliverable.


Objectives of Test Planning:
The objective for the test plan is to provide a set of tools to support the test team in various ways. Some of these benefits include:
     *        Reducing the risks that vital tasks will be omitted, mis-estimated or forgotten.
    *        Prioritize the tasks to be completed.
    *        Estimate the risks involved in the project (technical and procedural) and identify mitigation steps if possible.
    *        Organize the testing efforts.
    *        Monitor progress of the testing efforts and the project as a whole.
Designing a Test Plan - Test Planning Process:
    
Test planning is a process very like software project management, and often closely reflects the steps involved in project management.
       . The basic outline is to;

            1.   Analyze the project.
            2.   Identify the  tasks.
            3.   Determine priorities.
            4.   Schedule tasks.
            5.   Assign responsibilities.
            6.   Maintain and update the plan during execution.

Why do a tester need a Test Plan:     
                 
-  Writing a test plan gives tester a chance to collect thoughts and ideas. When writing a test plan make sure most areas are covered. 

-  Writing a test plan make the tester to understand the products well.  The tester has to drill down the requirements in more detail.

-  The test plan also give an oppurtunity for the tester to communicate with the test team, the developers and the test managers.

-  The test plan tells about the responsibility sharing of all the people involved in testing.

-  Writing the test plan will improve the test process and tools.

-  The tester has to tell the manager what they are doing.

-  The tester must know what to plan when the requirement or the design changes.

-  The test plan has to set other teams or partners expectation.



Advantages of Test Plan for Managers:

Sometimes testing the product may need additional resources such as machines, people, time and budget. By looking the test plan, the manager can arrange for those additional resources in advance. By that way, the testing can be done without any delays or breaks. Also sometimes, to test the particular item or component, it may need some additional resources. The manager can also make some arrangements for this situation with the help of the test plan. The manager can relocate the resources for that particular period.

Different audiences

The test plan is not only the chance to inform other testers, managers and others in the team of the particular tester's vision, also the chance to discover their perspectives. If there is only one lengthy test plan that addresses  every issue, it might be the trouble of getting people to read it. So it is always better to segment the planning, by that way documents can be created that can speak to the specific concerns of the individuals involved.
Test Plan - Objective & Benefits