User Tools

Site Tools


black_box_testing

Black Box Testing

Intro

Black Box Testing is a method of software testing that focuses on the input and output to determine the function of an application. The tester does not have any knowledge of neither the inner workings, nor the internal code structure or paths. This method by observing the return from a variety of inputs. The testers use this information to find patterns and infer the function of the software. It is sometimes referred to as Behavioral Testing or Specification-Based testing. Black Box Testing can be used on every level of software testing.

Process

There are a variety of ways to go about Black Box Testing, depending on the type, techniques and goals are. The general process starts off by looking at the specifications of the input required. Choose some valid inputs and invalid inputs, and observe if the software recognizes them . Then, determine what the result should be with a variety of inputs, and use these to construct tests to see if the system yields the expected outputs. Then observe if the results match the expectations.

Uses

This type of system testing finds how the software handles expected and unexpected user inputs, along with the response time,usability, and reliability issues. Black Box Testing is often used by white hat hackers in penetration tests. It is useful when the tester has no information about the workings of the system being attacked. The types of Black Box Testing include:

  • Functional Testing- used to test specific functions and crucial aspects of a system. Often implemented by software developers.
  • Non-Functional Testing- finds details about the software aside from the features. This type of testing can find how easy it is for the users to understand, performance in abnormal situations, and scalability.
  • Regression Testing- used to find if a code has changed with changes or updates to the software.

Pros and Cons

Some of the advantages to using Black Box Testing include that the tester does not need any technical knowledge or skills, it has low complexity and testers does not need to learn the details of the inner workings of the system. Additionally, there is a very low chance of false positives. Some of the disadvantages that can be experienced could be that it can be confusing to automate and to calculate test coverage.

  • Grey-Box Testing- method of testing software with partial knowledge of the functions and internal structure of the application.
  • White-Box Testing- testing software to find the internal structure, in contrast to the functionality.
black_box_testing.txt · Last modified: 2021/03/28 21:25 by alec