Breadth Testing

Breadth testing is a testing suite that will validate the full functionality of a product but does not test the product features in detail. Now let us understand the breadth testing from the integration point of view. Top down integration approach can either be depth-first or may be breadth-first testing all modules are refined at the same level of control. In reality a combination of both breadth-first testing and depth-first testing approach are used. 

In early stages of development all the modules may be developed only partially. These modules would be tested in breadth-first manner and over a period of time all these modules will be delivered with successive refinements which would be close to the full functionality of the product. Depth-first testing of one module is used to perform simultaneously with breadth –first testing. In the process of software development, it is necessary to test the functionality of the product so that the developers who can ensure that the product is being developed as per the requirements and demands of the customers as to validate its compatibility, scalability, reliability, security. Breadth testing is a test suite that validates the full functionality of a product. It does not test the product features in detail. It is one among the technique in software testing, which will be utilised by the team of knowledgeable and proficient testers to test the basic features of the software when properly checking and also verifying the functionality of the same.

Breadth Testing in Integration testing:

Integration testing may be done in many ways. But two of best possible way to implement on any software product are Top-down approach and Bottom up approach. Breadth-first testing or depth-first testing which can be done by the top-down approach. Top-down approach is an incremental approach to construct program structure, where modules are integrated by moving downwards from the control hierarchy starting with main control module. These modules subordinate to the main control module which are incorporated into the structure in either a breadth first or depth first manner. Breadth first integration incorporates all components to subordinate at every level while moving across the structure horizontally.

Uses of Breadth–First testing

While the software development and testing process in breadth testing is used to test and validate the full functionality of the software as well as to make sure that detailed testing is performed on the software. There are many testing techniques which use these test suites for many reasons. Breadth testing is important in testing the quality of the software. In some situations breadth testing is given more importance. There are some software testing techniques in which breadth testing suite is used in various context.

• Sanity Testing

It is a surface level testing where quality assurance engineer validates the product is working fine. Here breadth first is usually used to test and validate  the functionality of the product.

• Functional Testing:

It is a combination of both Breadth-first and Depth-first testing to check the software’s functionality. The main aim of breadth-first testing is checking all the features which will be tested in detail through depth-first testing.

• Automation:

Test automation is used of special software to control the execution of test and also comparison of actual with predicted outcomes. It uses breadth and depth testing to decide whether to automate end to end testing.

For example.

Top down  testing with Breadth-first are 

• M1
• M2,M3,M4
• M5,M6,M7
• M8