Question

What is a test case?

What are the characteristics of a good test case?

What is a driver?

What is a stub?

With what type of test is each most closely associated?

Answer 1

1) A TEST CASE is a set of conditions or variables under which a tester will determine whether a system under test satisfies requirements or works correctly. The process of developing test cases can also help find problems in the requirements or design of an application.

2)

A good Test Case satisfies the following criteria:

1. Easily identifiable with its name;
2. Simple and specific (any one in the test team should be able to execute the Test Cases without the author help);
3. Reasonable probability of catching an defect;
4. Traceable to requirements;
5. Compliant to regulations;
6. Exercises an area of interest;
7. Does interesting things;
8. Doesn't do unnecessary things;
9. Explicited pre-conditions;
10. Defined test data input;
11. Clear, concise, and complete (no assumptions in Test Case description, steps, expected result etc.);
12. Written without grammar errors;
13. Written without ambiguous words;
14. Always list expected results;
15. Always list post condition;
16. Neither too simple nor too complex;
17. Not redundant with other Test Cases;
18. Repeatable and reusable;
19. Minimize technical support;
20. Written with the help of Test Case design methods;
21. Allows isolation and identification of defects;
22. Makes defects obvious; and
23. Assure quality.

3) A driver is basically a piece of code through which other programs or pieces of code or modules can be called. Drivers are the main program through which other modules are called.
If we want to test any module it is required that we should have a main program which will call the testing module. Without the dummy program or driver, the complete testing of the module is not possible.
Drivers are basically called in BOTTOM UP testing approach. In bottom up testing approach the bottom level modules are prepared but the top level modules are not prepared. Testing of the bottom level modules is not possible with the help of main program. So we prepare a dummy program or driver to call the bottom level modules and perform its testing.

4) Stubs are basically used in TOP-DOWN approach of integration testing. In this approach, the upper modules are prepared first and are ready for testing while the bottom modules are not yet prepared by the developers.
So in order to form the complete application we create dummy programs for the lower modules in the application so that all the functionalities can be tested.

5) **Answered as part of 3 and 4**

Drivers -> BOTTOM UP testing approach

Stub -> TOP-DOWN testing approach