All most all the companies are following IEEE Standard 
format for their different documents during Test life cycle.

Document                 Standard
---------                ---------
Testcase                  IEEE 829
TestPlan                  IEEE 829

But none of the companies are follwing the complete formate 
of the Tesecase or TestPlan.Simply they are customizing the 
format as per thier needs.

In our company we are follwing below format.

1.Testcase ID 
2.Priority
3.Type of TC(+ve,-ve,etc...)
4.Description of the testcase
5.Steps to execute
6.Expected result
7.Pass/Fail criteria
8.Bug Number
9.Executor

hi to all,

 
 In our company we are following format

  1.Testcase ID
  2.Type of Testcase
  3.Testcase Description
  4.Expected Results
  5.Status

Hi,

in our company we follow test case format as:

1.  Test case ID
2.  Bug Id
3.  Status
4.  Priority
5.  Severity
6.  Title
7.  Steps to Perform
8.  Expected Results
9.  Actual Result
10. Comments

if i am wrong pl. tell me

Meenakshi,

Are the following details required in Testcase format?

I dont think so.....Of course bug ID is o.k,but rest of the 
fields are not required..because these fields will make 
your testcase too longer..


3.  Status
4.  Priority
5.  Severity

SNO
DESCRIPTION(verify +ve and _ve statements)
INPUT DATA values(max, min if u go for bva)
ACTION means mouse click or click on tab
EXPECTED DATA
ACTUAL DATA
RESULTS
TEST CASEID

Ofcourse, their are some IEEE std's for testcases, 
testplans.

1)Some companies follows,can manage.

2)But it's impossible for small scale companies to follow 
them.So they have their own std's.

If you compare them, they are almost same with little 
modification...

So, you can talk about the Format's you have studied during 
college day's or what you had in you previous organization.