Browse Article

Software Testing Techniques

June 3, 2016 | Author: | Posted in Careers

Different Techniques Of Software Testing

There are different techniques that can be used for software testing. This chapter temporarily explains the types of software testing

Black-Box Testing

The technique of analyzing without having any information of the interior technicalities of the program is called black-box analyzing. The specialist is unaware to the program structure and does not can get to the source code. Typically, while performing a black-box analyze, a specialist will interact with the body interface by providing information and analyzing results without knowing how and where the information is worked upon.


  1. Well suited and efficient for huge code sections.
  2. Code accessibility is not required.
  3. Clearly distinguishes customer’s viewpoint from the producer’s viewpoint through clearly defined positions.
  4. Huge numbers of reasonably skilled evaluators can analyze the program with no information of execution, programming language, or operating-system.


  1. Restricted protection, since only a selected number of testing circumstances is actually performed.
  2. Ineffective analyzing, due to the fact that the specialist only has limited information about a program.
  3. Sightless protection, since the specialist cannot target specific code sections or error-prone areas.
  4. Test cases are difficult to design.

White-Box Testing

White-box tests the detailed research of inner reasoning and structure of the rule. White-box tests also called glass examining or open-box examining. In order to perform white-box examining on an application, a specialist needs to know the inner technicalities of the code.

The specialist needs to have a look inside the source code and find out which unit/chunk of the code is acting unnecessarily.


As the specialist is well aware of the source rule, it becomes very readily available out which type of data can help in examining the application effectively.

It helps in improving the rule.

Extra lines of rule can be taken off which can bring in invisible problems.

Due to the tester’s information about the rule, maximum coverage is accomplished during test situation writing.


Due to the fact that a experienced specialist is needed to perform white-box examining, the costs are improved.

Sometimes it is difficult to look into every place and area to discover out invisible mistakes that may lead to further problems, as many routes will go untried.

It is difficult to maintain white-box examining, as it requires specific resources like rule analyzers and debugging resources.

Grey-Box Testing

Grey-box assessments a technique to analyze the program with having a small information of the interior technicalities of a software. In software examining, the term the more you know, the better provides a lot of weight while examining a software.

Mastering the sector of a system always gives the specialist a benefit over someone with restricted sector information. Compared with black-box examining, where the specialist only assessments the application’s user interface; in grey-box examining, the specialist has access to design records and the data source. Having this information, a specialist can get a better analysis of data and analyze circumstances while making an analysis plan.


Provides mixed benefits of black-box and white-box testing wherever possible.

Greyish box evaluators don’t depend on the resource code; instead they depend on customer interface meaning and efficient requirements.

Based on the restricted information available, a grey-box specialist can design excellent analysis circumstances especially around interaction methods and data type managing.

Quality is done from the perspective of the consumer and not the developer.


Since the access to resource program code is not available, to be able to go over the program code and analyze protection is restricted.

The assessments can be repetitive if the software developer has already run the analysis case.

Testing every possible feedback flow is impractical because it would take an irrational amount of time; therefore, many program routes will go untried.

More Related Video:

Software Testing- Quality Control And Quality Assurance

This article would be helpful for Student Software Testing Reviews.

Article Source


this is training and placement institute in pune .

This author has published 44 articles so far.