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 IEEE FORMAT test case within the Testing Templates forums, part of the Software Testing category; please any body send me a IEEE FORMAT test case NOTE : [This question was asked by ali]...
|
|||||||
|
|||
|
Re: IEEE FORMAT test case
After selection of all possible test case titles, corresponding test engineers are documenting that test cases with complete information in IEEE829 format: test case document format:
test case id: unique number or name test case name: previously selected test case title feature to be tested: the name of corresponding module functionality test suit id: the name of test batch id, in which batch this case is a member. Priority: the importance of this test case w.r.t functionality test environment: required h/w and s/w to execute these test cases. Test effort: time to execute this test case eg: 20 min is average time to test this test case test duration: date (expected) by when the test case would be completed. Pre-condition necessary tasks to do before starting the test execution test procedure: a step by step procedure to execute this test case step no. Action i/p required expected actual result comment test case pass / fail criteria: when this case is "pass", when this case is "fail" note: in general, the test engineers are not filling 11 fields format for every test case. They are filling some of the mandatory fields for every test case document. Because maximum test cases consist of some values for some of the fields and time is an important factor to save. Last edited by bvani; 02-02-2007 at 12:51 PM. |
|
|||
|
Re: IEEE FORMAT test case
Hi JobHelper here is IEEE829 format
According to the IEEE Standard 829 - 1998: A test plan shall have the following structure: a) Test plan identifier; b) Introduction; c) Test items; d) Features to be tested; e) Features not to be tested; f) Approach; g) Item pass/fail criteria; h) Suspension criteria and resumption requirements; i) Test deliverables; j) Testing tasks; k) Environmental needs; l) Responsibilities; m) Staffing and training needs; n) Schedule; o) Risks and contingencies; p) Approvals. |
![]() |
|
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Use case statement and Test Case | JobHelper | Testing Issues | 4 | 01-16-2009 03:48 AM |
| Format for writting test cases | JobHelper | Test Cases | 19 | 07-25-2008 08:20 AM |
| Good automated test case | Lokesh M | Test Cases | 3 | 02-12-2007 03:11 PM |