Integration Testing

Integration testing should be carried out by persons other than the designers of programs and can also verify the proper functioning of the correct program design and interpretation. (3) In addition to these 10 principles: The test can be used to show the presence of errors, but never their absence. The main difficulty of the testing process is to decide when to stop. Avoid unplanned test cases, not reusable and trivial unless the program is really easy.

4. You may want to visit Samsung to increase your knowledge. A necessary part of a test case is the definition of outcome. The test cases have to be written not only for valid input conditions and expected but also for invalid and unexpected conditions. The test cases have to be written to generate the desired output conditions.

The number of undiscovered errors is directly proportional to the number of errors discovered. The tests should begin with “small” and progress towards “big.” With the exception of unit tests and integration, a program should not be tested by the person or organization that developed it. The tests should be performed by a independent team. 2.2 Types of Testing Unit Testing: The test unit focuses on the module. Using the detailed design description as a guide, to test the important control paths in order to discover errors within the module. The unit test makes extensive use of techniques white box testing. (4) Integration Testing: The objective is to take the modules tested in the unit test and build a program structure that is in accord with the dictates of the design.