Home > Integration, Testing, Unit > Unit Test Vs Integration Test

Unit Test Vs Integration Test

Sl.No

Unit Test

Integration Test

1

Unit test is the test of the software elements at the lowest level of development.

Performed to examine how units interface and interact with each other with the assumption that the units and the objects (e.g., data) they manipulate have all passed unit tests.

2

Unit test plan should occur concurrently with the software design activity

Integration test schedule depends upon the development and integration schedules for software units, hardware, and other components. For large systems, software integration test planning may require close coordination among all system personnel to ensure that the overall test objectives are achieved by the selected test strategy.

3

Test planning – Establish the objectives of the unit test, the strategies to be employed, the coverage requirements, reporting and analysis, and closeout of anomalies.

Test planning – Establish the objectives of the software integration test, the strategies to be employed, the coverage requirements, reporting and analysis, and closeout of anomalies. Ensure that interface testing of reused software to other system software is planned

4

Trace test design, cases, procedures, and execution results to the unit designs

Trace test design, cases, procedures, and execution results to software requirements

5

Perform unit test

 

Ø      Check individual software units for typographical, syntactic, and logic errors to ensure that each correctly implements the software design and satisfies the software requirements; execute the test cases; analyze results to verify anomalies; recommend changes to software design or code; and conduct re-testing as necessary.

Perform integration test.

Ø      Check the inter-unit communication links and test aggregate functions formed by groups of units.

Ø      Confirm that anomalies during test are software anomalies, and not problems detected for other reasons.

Ø      Ensure any changes to software requirements, software design, or code is made. Conduct retesting as necessary.

Ø      Conduct functional, structural, performance, statistical, and coverage testing of successfully integrated units after each iteration of software integration and successful testing of interfaces and interactions

 

Advertisements
  1. No comments yet.
  1. July 1, 2009 at 5:31 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: