Test Planning
Printed From: One Stop Testing
Category: Types Of Software Testing @ OneStopTesting
Forum Name: Manual Testing @ OneStopTesting
Forum Discription: Discuss All that is need to be known about Manual Software Testing and its Tools.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=3351
Printed Date: 18Jul2025 at 9:47am
Topic: Test Planning
Posted By: tanushree
Subject: Test Planning
Date Posted: 27Oct2007 at 5:19am
Test Planning: After completion of test initiation, TL of the
testing team concentrate on test planning to define �What to test�,
�How to test� ,�When to test�, �Who to test�?. Test plan author follows
below work bench (process) to prepare test plan document.
1.Team formation: In general test planning process starts with testing team formation. In this step test plan author depends on below factors a) Availability of testers b) Test duration c) Availability of test environment resources Case Study: Test duration C/S, Web, ERP ---- 3 to 5 months of functional & system testing Team size 3:1 2.Identify tactical risks: After completion of team formation test plan author study possible risks raised during testing of that project Ex Risk 1: Lack of knowledge on domain Risk 2: Lack of budget (time) Risk 3: Lack of resources Risk 4: Delay in delivery Risk 5: Lack of development process rigor (seriousness of dev team) Risk 6: Lack of test data (some times test engg conducting Ad Hoc testing) Risk 7: Lack of communication 3) Prepare Test Plan: After completion of team formation and risk analysis test plan author prepare test plan document in IEEE format. FORMAT: 1) Test Plan ID: Unique number 2) Introduction: About project and test team 3) Test Items: Modules/Features/services/functions 4) Features to be tested: Responsible modules to prepare test cases 5) Features to be not tested: which ones and why not? 6) Approach: Required list of testing techniques (depends on TRM) 7) Feature Pass or Fail Criteria: When a feature is pass when a feature is fail 8) Suspension Criteria : Possible abnormal situations raised during above features testing 9) Testing Tasks (Pre requisite): Necessary tasks to do before starts of every feature testing 10) Test Deliverables: Required test documents to prepare during testing 11) Test Environment: Required HW and SW including testing tools 12) Staff and Training Needs: Names of selected test engineers 13) Responsibilities: Work allocation 14) Schdule: Dates & Time 15) Risks and Mitigations : 16) Approvals : Signatures of test plan author, QA or PM |
Replies:
Posted By: thangavelshanmu
Date Posted: 13Jun2008 at 10:49pm
|
NICE TO READ BY KS THANGAVEL |
Posted By: getzephyr
Date Posted: 17Jul2008 at 1:13am
|
Nice information!
------------- |
Posted By: ethikumar
Date Posted: 20Jul2008 at 10:01pm
| Good information for Tester |