vinod

• Feb 18th, 2007

 

the standard things are

test case num,UCD ref num,description,expected value,actual values,result.

GURU

• Mar 1st, 2007

 

What Vinod said is rite...!

Depending on companies it may have other fields module no, version no, comments, severity, priority colums.....

GURU
guruqualityguru@gmail.com

Sunny

• May 11th, 2007

 

I can say important contents in test case followed by description

1.Test case ID : It is identification of a test case for futher reference

2.URL : Uniform resource location nothing but address of a function/field for validating where it is located
 
3.Steps : This is for understanding how to excute test case

4.Expected : This is very importent based on this we can ensure that testcase is   passed

5.Actual : This is filled after excuting the test case what happend in test case excution

6.Remarks : Nothing but a result difference between Expected and Actual ( pass/Fail)

rajmohan23

 Profile Answers by rajmohan23 Questions by rajmohan23

• Sep 1st, 2009

 

The Standard Format

test case id
validation filed name
test case description
test case steps
test data
test action
expected result
actual result

The test case design depends upon company to company we
are following these steps.

Update me if I am incorrect

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 12th, 2009

 

- Test case id
- Priority
- Severity
- Requirement id
- Tester name
- Created date
- Last updated
- Reviewed date
- Reviewed by
- Target build
- Defect reference number
- Execution date
- Test status (Pass; Fail)
- Title
- Objective
- Prerequisite(s); Precondition(s)
- Environment
- Test steps
- Expected result
- Actual result
- Comments
- Supporting document(s)