This is a discussion on plz explain me about the terms related to testplan within the Testing Tutorials forums, part of the Articles and Tutorials category; Testplan explains core functionality of module , functional areas , resources , estimated hours , risk management , deliverable etc....
|
|||||||
| Testing Tutorials Testing Tutorials and Articles Discussions |
![]() |
| LinkBack | Thread Tools | Search this Thread |
|
|||
|
Hi Simmy,
I am trying to clear your doubts. If not clear ask me to clear once again. Let take simple example to clear your doubts.Suppose that our client requiremet is like that he wants to Create and Track records all of his customers and their Sales Quatations.This requirement is mentioned on SRS. Here Core Functionality (Modules): Customer Card and Sales Quation Card Functionalities or areas for which we are going to write test cases are: On Customer Card: 1. Creation of Customer 2. Search of Customer 3. Closing of Customer Card On Sales Quatation Card: 1. Creation of Sales Quatation 2. Search of Sales Quatation 3. Closing of Sales Quatation Card Resources: Means who will involve in wrting test cases, executing test cases and reporting the issues. Normally we mention Tester(s) Name. Estimated Hours: On the basis of functionalities, we are estimating how much time will take to write Test cases, execute that cases, reporting issues and number of cycle require. Total time involve in this is our estimated time. We are using different technique to estimate the time like COCOMO, WBS (Work bench Structure) etc. Risk Management: What are the risk factor involve during this activity, we have to mention. for Example: Change Request will cause the scheduled date, Entry/exit criteria are not met etc. Deliverables: At the end of all activites(System Test Plan to Release) , what we'll deliver/ release. For Example: We'll release Test Plan, Test Cases, Bug Reports, Known bugs etc. Assumptions: We define entire assumptions that we will consider during this activity. for Example: Unit testing must be performed by the developers,All the referenced document must be signed off etc Dependencies: If our software requirement any third party tool, we have to mentioned here. Automation Tools used: Whether we are using Automation tool or not. If using, which tool and for whcih functionilties. Manual Test: We are using Manual approach for which functionalites. Aprt from these terms, we are using more terms and that can't be possible to define here and might not be used in all company. So, either go through any General System Test Plan for reference and ask your query or post terms that is used in your company, I'll try to clear them. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Tutorial on Silk Test | spriya279 | Testing Tutorials | 2 | 02-15-2007 07:31 PM |
| Catalog of Compiler Construction Products - Eighteenth Issue | cccp@transformal.com | Tech FAQ | 0 | 05-01-2004 08:00 AM |
| [FAQ] FileMaker Pro - database for Macintosh and Windows | Martin Trautmann | Tech FAQ | 0 | 04-17-2004 08:26 AM |