I would suggest you to look at recent post "how to Design test cases?". You will see there that different companies and different persons use this term little bit different.
Let me explain what is the difference. Let's take login test case for example. Your test case may or may not describe that user should be created, access rights configured, client application installed, server configured. Also validation steps and pass/fail criteria may be described or supposed as self-evident.
?:the art of a constructive conflict perceived as a destructive diagnose.
Originally posted by rssenthilkumar: I want to know about the Test case
Please Clarify my doubts
"what is Test Case?" give the formal answer
<font size="2" face="Verdana, Arial, Helvetica">Test case is a document which has input,some execution conditions and output(expected results).
The execution conditions are nothing but what exactly user wants given to us in the from of SRS (software requirement specification)
The Case will look some like this
Testcase ID : To identify particular module
TestDescription : What we r going to test(what feature we r going to test)
Expected results : What the exact out put shuold be.
actual results : What the output is (obtained)
Pass/Fail : If expected and actual results are same than it Pass or else it is Fail