Golgappa.net | Golgappa.org | BagIndia.net | BodyIndia.Com | CabIndia.net | CarsBikes.net | CarsBikes.org | CashIndia.net | ConsumerIndia.net | CookingIndia.net | DataIndia.net | DealIndia.net | EmailIndia.net | FirstTablet.com | FirstTourist.com | ForsaleIndia.net | IndiaBody.Com | IndiaCab.net | IndiaCash.net | IndiaModel.net | KidForum.net | OfficeIndia.net | PaysIndia.com | RestaurantIndia.net | RestaurantsIndia.net | SaleForum.net | SellForum.net | SoldIndia.com | StarIndia.net | TomatoCab.com | TomatoCabs.com | TownIndia.com
Interested to Buy Any Domain ? << Click Here >> for more details...

what is the gendral format for test case?

Answer Posted / mohankanth

Test case ID - The test case id must be unique across the
application
Test case description - The test case description must be
very brief.
Test prerequisite - The test pre-requisite clearly
describes what should be present in the system, before the
test can be executes.
Test Inputs - The test input is nothing but the test data
that is prepared to be fed to the system.
Test steps - The test steps are the step-by-step
instructions on how to carry out the test.

Expected Results - The expected results are the ones that
say what the system must give as output or how the system
must react based on the test steps.
Actual Results – The actual results are the ones that say
outputs of the action for the given inputs or how the
system reacts for the given inputs.
Pass/Fail - If the Expected and Actual results are same
then test is Pass otherwise Fail.
The test cases are classified into positive and negative
test cases. Positive test cases are designed to prove that
the system accepts the valid inputs and then process them
correctly. Suitable techniques to design the positive test
cases are Specification derived tests, Equivalence
partitioning and State-transition testing. The negative
test cases are designed to prove that the system rejects
invalid inputs and does not process them. Suitable
techniques to design the negative test cases are Error
guessing, Boundary value analysis, internal boundary value
testing and State-transition testing. The test cases
details must be very clearly specified, so that a new
person can go through the test cases step and step and is
able to execute it. The test cases will be explained with
specific examples in the following section.

Is This Answer Correct ?    9 Yes 1 No



Post New Answer       View All Answers


Please Help Members By Posting Answers For Below Questions

'This life cycle model is driven by schedule and budget risks' this statement is best suited for.

1064


What are the Difficulties you found while testing your module ? plese give the possible difficulties.

2416


What test plans consists of?

1048


What are enter & exit criterias of a test paln?

1247


What are the Achievements in previous company...as a software Test engnineer...Anybody can give me answer..Thanks in advance..

2217


What is equivalence partitioning testing?

1060


What are the layers of FCOE Protocol?

1905


What is the bottom-up approach?

1121


What the meaning of breath testing is?

1057


Explain the term bug.

1185


Mention what the difference between a 'defect' and a 'failure' in software testing is?

1083


What is outputs?

1014


What is data validity?

1022


What is a variant?

1056


Mention what the meaning of breath testing is?

1119