Black Box Techiques

From PheonixSolutions
Jump to navigation Jump to search

Black Box Testing Techniques

[edit]

With no internal knowledge of an application, structure is important to ensure that the test covers all necessary cases. Some common techniques for performing a black box evaluation include:

Equivalence Class Testing: Allows applications to follow the same flow of control for certain types of input. For example, an application that is supposed to be accessible only to adults may terminate if a user enters an age under 18. Additionally, tools with limited service may be terminated for countries or postal codes outside of that region. In equivalence class testing, the tester identifies classes that produce the same results and tests only the values ​​within those classes.

Boundary Value Evaluation: A limit is an input that causes an application to change from one control flow to another. For example, ages 17 and 18 are the threshold for adulthood; a 17-year-old's application may be rejected, but an 18-year-old's application may be accepted. Boundary evaluation tests these inputs to ensure that the system is handling these edge cases correctly.

Decision Table Testing: Applications can be designed to make decisions based on combinations of inputs. For example, users over the age of 18 who live in certain regions may be able to access the Application. Testing a decision table involves listing each combination of inputs and its expected result, and developing test cases to validate each combination.

State Transition Evaluation: Applications can be designed to change state under certain conditions. B. Lock a user's account after a certain number of failed authentication attempts. Evaluating state transitions is about identifying these situations and developing test cases to verify them.

Error Checking: This form of evaluation checks for common errors that developers may make while building an application. This often involves sanitizing the input and ensuring that assumptions about the input are enforced. For example, a tester can check whether the developer correctly handled the entry of zero into a numeric field or restricted the character set of a name to only the characters and symbols that are allowed in a name.