Prepare for your Next Interview
|
Welcome to the Geeks Talk forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact us. |
This is a discussion on Pls explain me about this Documentation within the Testing Issues forums, part of the Software Testing category; 1. What isTesting the functionality of the applications developed to ensure it confirms to specifications & documentation? 2. What is Understanding the requirements? 3. What is test case designing about ...
|
|||||||
|
|||
|
Pls explain me about this Documentation
1. What isTesting the functionality of the applications developed to
ensure it confirms to specifications & documentation? 2. What is Understanding the requirements? 3. What is test case designing about the project? 4. What is Test case Execution? 5. What is Test case result evaluation? 6. What is Logging the defect in defect tracking sheet? 7. What is Follow up with the development to make sure that the defect resolved as early as possible? 8. What is Documentation of software? Pls any one explain me wht is wht? |
| Sponsored Links |
|
|||
|
Re: Pls explain me about this Documentation
1) Not very sure I understood the question, but I think the most probable answer is "Process Testing"
2) Understanding the business logic behind the requirements defined in the SRS. 3) Identifying the scenarios and steps required to test the s/w. 4) Applying the identified scenarios & steps (Test Cases) to the s/w application under test. 5) Evaluating the outcome fome the s/w application on Test Case Execution. 6) Describing the mismatches between test case expected and test run result for the Development team to resolve the same. 7) Tracking the progress of resolution process and working with the responsible developer to get the defect resolved. 8) Documentation of s/w could be making notes of everything and anything in the s/w development process.
__________________
Lack of WILL POWER has caused more failure than lack of INTELLIGENCE or ABILITY. -sutnarcha- |
| The Following User Says Thank You to sutnarcha For This Useful Post: | ||
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| role of documentation in qa ? | jainbrijesh | Testing Issues | 3 | 06-15-2009 08:12 AM |
| UML Documentation | darshil.safari | Information Technology | 2 | 08-20-2008 02:04 PM |
| IEEE 829 test plan documentation standard contains all of the following except | jainbrijesh | Testing Issues | 1 | 12-21-2007 09:32 AM |
| Oracle Documentation | dgopinath_1974 | Oracle Certification | 2 | 11-23-2007 01:03 AM |
| PostgreSQL Documentation | Jim.Anderson | SQL | 0 | 12-11-2006 08:31 PM |