Skip to main content

Component Testing

Component Testing is the way to testing the individual component separately. Component Testing is also called module testing or program Testing. Suppose any system have 5 components then all 5 component tested separately with efficiency called Component Testing.
Because of Component Testing done separately so here we use Driver and Stubs to provide them working same as system. Driver and Stub work like the missing software in Component Testing.

Let me explain it suppose any software have 3 component suppose P, Q and R. Only Q module developer and Manager told you to test it. How you will test it if Module P and R not developed. So here you can replace Module P and R with the dummy code these dummy code called Driver and Stub.

Stub is called from the tested software. In above example Module P behave like Stub.
Driver is calls the tested software. In above example Module R behave like Driver.

Component Testing perform just before the Integration Testing to make sure every Component of the software working correctly. 
Labels:

Comments

Post a Comment

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.
Post a Comment
Read more

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.
Post a Comment
Read more

Integration Testing

When all small unit of code combined together or we can say integrate together then perform the testing between the interface of these units to verify that are these unit working fine when these are combined. Integration Testing occur after Unit Testing. In Unit Testing , developer concern only over the each module and fixes all error in that but developer not focused that what is the effect of bug fixes in other modules. Each Unit is developed by different different programmers so in Integration Testing, We will test the data communication between these Units.
Post a Comment
Read more