Stubs and Drivers in Software testing

They are computer programs which act as a substitute for some other modules (which are not available for testing). These computer programs will simulate the functionalities of the other modules thereby facilitating the software testing activity. What are stubs? Stubs are basically used in a TOP-DOWN approach of integration testing. […]

Bottom-up Integration

The bottom-up approach requires the lowest-level units to be tested and integrated first. These units are frequently referred to as utility modules. By using this approach, utility modules are tested early in the development process and the need for stubs is minimized. Advantages: The strengths of Bottom-Up Testing overcome the […]

Top Down Integration

It requires the highest-level modules to be tested and integrated first. This allows high-level logic and data flow to be tested early in the process and it tends to minimize the need for drivers. Advantages: The strengths of using the Top-Down strategy is that the top layer provides an early […]

Big Bang Integration Testing

When we are in love with technology and research, we try to deteriorate with the new aspects of the technology. Approaching with the new set of mind on the old thing leads to the development of new technology or new invention so it is really very much important to be […]

Integration Testing

Integration Testing is a level of software testing where individual units are combined and tested as a group. The purpose of this level of testing is to expose faults in the interaction between integrated units. Test drivers and test stubs are used to assist in Integration Testing. Integration testing: Testing […]

Basis Path Coverage

A path represents the flow of execution from the start of a method to its exit. A method with N decisions has 2^N possible paths, and if the method contains a loop, it may have an infinite number of paths. Fortunately, you can use a metric called cyclomatic complexity to […]

Branch Coverage

A branch is the outcome of a decision, so branch coverage simply measures which decision outcomes have been tested. This sounds great because it takes a more in-depth view of the source code than simple statement coverage, but branch coverage can also leave you wanting more. Determining the number of […]

Statement Coverage:

Introduction Code coverage is a way to measure the level of testing you’ve performed on your software. Gathering coverage metrics is a straightforward process: Instrument your code and run your tests against the instrumented version. This produces data showing what code you did—or, more importantly, did not—execute. Coverage is the […]

Condition Coverage Testing

This is closely related to decision coverage but has better sensitivity to the control flow. However, full condition coverage does not guarantee full decision coverage. Condition coverage reports the true or false outcome of each condition. Condition coverage measures the conditions independently of each other. Other control-flow code-coverage measures include […]

Structural Testing

Structural testing is the type of testing carried out to test the structure of the code. It is also known as White Box testing or Glass Box testing. This type of testing requires knowledge of the code, so, it is mostly done by the developers. It is more concerned with […]