
- Forum
- Testing
- Software Testing
- software testing documents
software testing documents
This is a discussion on software testing documents within the Software Testing forums, part of the Testing category; Hi every1 there I am Diana can any one explain me the initial documents to the final documents used in ...
-
09-27-2007, 04:49 AM #1
- Join Date
- Sep 2007
- Answers
- 1
software testing documents
Hi every1 there
I am Diana can any one explain me the initial documents to the final documents used in a testing process clearly with the contents in them and their purpose
-
11-06-2007, 09:59 AM #2
- Join Date
- Nov 2004
- Answers
- 3
These are the documents mostly used in Testing life cycle.
1. Test Strategy - contains Intro abt the prj, various testings involved in the prj (Unit, system, Integration, E2E, performance, UAT etc.), approach for each testing, Entry/Exit criterien for each testing.
2. Test Plan - This doc will be separate for each testing. This contains intro abt the Application, inscope and out of the scope for testing, teams involved, roles and responsibilities, schedule, risks, hardware, software used in the prj, templates used for test cases, defect tracking and daily status reports in case of manual testing, tool that is going to be used in case of automation.
3. Test case document - This contains the version no, author and reviewer details, Typically all the test cases will be written under the following headings. S.No, Requirement no, Description, Expected result, Pass/Fail, If fail reason, Tester.
4. Defect Tracker - This will look like as follows.
Defect no., Priority, Status, Module/screen, Description,logged date, closed date, raised by, assaigned to, comments.
5. Daily status report - This doc contains the no. of test cases/scenarios planned, executed, passed, failed, issues if any, no. of defects raised, priority, environment downtime if any.
Vamsi

Reply With Quote





