1) Test Case: It is a document designed to exercise/test both internal LOGIC designed, interfaces in the system designed, & external

requirements (Performance/Load/Stress) designed and which contains step by step procedure to test the functionalities of an application/Utility, Perquisite to test the functionality, Test Data, Expected Results are defined, Test Type, Actual Results are recorded, Test Case Pass/Fail and the Possible Reasons for the failure (Causes) . 2) Advantage by maintaining Test Cases: As the Main Purpose of test cases is not to miss testing of any functionality and requirement. As it is performed in a sequential way, one step by-step, i.e. the second step would be relevant to the previous one so there wont be any chance for the tester to miss any requirement or functionality. 3) What is a Good Test Case? 1. Readable/Understandable/ 2. Accurate- Tests what is designed to test (i.e. the Objective of the test, One test Case should have only one expected result) 3. Repeatable, Reusable- Keeps on going 4. Traceable- to a requirement (Order of Test Cases should be traced to an Functionality) 5. Appropriate- for Test Environment, testers 6. Self Standing- independent of the writer (understandable for any layman who His new to the system) 7. Self cleaning- picks up after itself. 8. Economical-no unnecessary steps 9. Order of Test cases should match business scenarios 4) What is to followed while writing/Designing test cases?/Test Designing 1. Test Cases Covers all Features/Functionalities of any application/ Utility. 2. Completeness of test. 3. Quality 4. Validate the quality of test cases by comparing with system requirement documents. 5. There is balance between functional tests & non-functional tests. 6. There is a balance between black box & White box testing. 7. Finally the static testing for Test Case document, i.e. documenting test cases written, for Formal Reviews & inspection to Validate the Quality of the Test Case Document whether it covers all the Critical test cases. 5) What is Repeatable/reusable Test Case? Login Test Cases written for a banking application should be able work for a Web application login process (yahoo login, etc). 6) Test Data: Use Black Box Techniques such as Equivalence Class/Partitioning Boundary Value Analysis(BVA) 7) Test Environment: Before executing the test cases, the ensuring of set up as hardware, Software, Tools, Data, etc., are ready in the correct state to enable the tests to be conducted.

Test Execution: The Processing of a test Case by the software under test or AUT, producing an outcome. 8) When to Stop Test Execution: Test Manager Will consider the following Factors Deadlines, e.g. release deadlines, testing deadlines; Test Cases completed execution with certain percentage passed; Test budget has been depleted; Coverage of code, functionality or requirements reaches a specified point; or Bug rate falls below a certain level; or Beta or alpha testing period ends; When the risk in the project is under acceptable limit; 10) Start Test Execution: As soon as we have a single requirement with the objective for trapping Requirements-related defects (Static testing) as early as they can be identified. 11) Who Performs the Tests? Unit Testing- Development Team Integration testing developers, test team System testing- test team Adhoc testing test team 12) Quality Control: It is a system of maintaining standards/Quality in manufactured products by testing a sample of the output against the specifications. 13) Software Testing is a Process (it is not a phase) of analyzing (Static) or operating (Dynamic) software for the purpose of finding bugs. 14) What is Defect? The Software doesnt do something that the product specification Says (mentions) it should do. The Software does something that the product specifications says it shouldnt do The Software does something that the product specification doesnt mention The software doesnt do something that the product specification doesnt mention but should do (e.g: Feature/Suggestion type Severity ). Difficult to Understand, hard to use, slow etc 15) Difference between Failure and Defect? 16) What is Test Execution Summary Report & Test Incident Report? Test Execution Summary is quantitative measure of the degree to which a system is tested. That is to know the effectiveness of the testing process in identifying the defects for a given project.