Monday, March 12, 2012

TestCases - Q/A

1. What is a Test Case
Test Case is a document which describes the pre-requisite of input action and an expected result to validate that feature of the system/application is working correctly or not.

2. What do you mean by Test Cases?
Test cases typically describe test inputs, execution conditions, pre-requisite, expected result and actual result.

Known Input :-: Pre-Condition
Expected Output :-: Post Condition

3. Why do we write Test Cases?
 We have not one or two benefits of writing test cases, but we have lots of things to get a application bug free, when we jot down the test cases in the document from the process of thinking. It increase the efficiency of executing tester, as many as possible bugs can be found out in earlier phases of testing. Testing is not too simple neither too complex. 

Note: But for every single test case we have should only one expected result.
Test cases is implemented to validate the Application / Product is performing in the intended behavior. 

4. How to write test cases?
The basic objective of writing test cases is to validate all the requirement of the application. It will minimizes the Ad-Hoc approach in testing.

5. What is the difference between positive and negative test cases?
For each and every requirement we have at least two test cases - 1. Positive and 2. Negative test cases. This can be achieved by techniques used for writing test cases like Boundary Value, Equivalence Partitioning.

6. How will you check that your test cases covered all the requirements?
Relationship between Test cases and Requirements when clubbed together the another very important document is created known as Requirements Traceability Matrix

No comments:

Post a Comment