Often asked in testing interviews , does the BB-testing means just testing of the functionality.Well as a definition we can say that in BB-testing we consider the system as black box and we are not concerned with the internal structure of it. We just need to give input and see the response of the system. BB testing is used at all the level of testing (i.e - integration, system , etc). Here the requirement of any application is analysed and then the testing is performed by tester.
Test design techniques
Typical black-box test design techniques include:
Equivalence partitioning : It divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. For each partitions the behavior of the system remains the same.It avoids repetition of cases as for all the data in the given range the behave of the system will be same.divides the input data of a software unit into partitions of equivalent data from which test cases can be derived.
Boundary value analysis : This techniques is used to check the boundary values of the system. Boundary values means the behave of the software will change at these values. So there is maximum possibility of errors at boundaries.
Cause–effect graph : a cause–effect graph is a directed graph that maps a set of causes to a set of effects. The causes may be thought of as the input to the program, and the effects may be thought of as the output. Usually the graph shows the nodes representing the causes on the left side and the nodes representing the effects on the right side. There may be intermediate nodes in between that combine inputs using logical operators such as AND and OR. Its used basically in designing test cases based out of functionality.
Error guessing : error guessing is a test method in which test cases used to find bugs in programs are established based on experience in prior testing.The scope of test cases usually rely on the software tester involved, who uses past experience and intuition to determine what situations commonly cause software failure, or may cause errors to appear. Typical errors include divide by zero, null pointers, or invalid parameters.
Decision table testing : Its also a kind of Cause -effect technique where we create a decision based out of certain inputs. Each decision corresponds to a variable, relation or predicate whose possible values are listed among the condition alternatives. Each action is a procedure or operation to perform, and the entries specify whether (or in what order) the action is to be performed for the set of condition alternatives the entry corresponds to.
Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent ones -
Functional testing - This black box testing type is related to functional requirements of a system; it is done by software testers.
Non-functional testing - This type of black box testing is not related to testing of a specific functionality , but non-functional requirements such as performance, scalability, usability.
Regression testing - Regression testing is done after code fixes , upgrades or any other system maintenance to check the new code has not affected the existing code.
Test design techniques
Typical black-box test design techniques include:
Equivalence partitioning : It divides the input data of a software unit into partitions of equivalent data from which test cases can be derived. For each partitions the behavior of the system remains the same.It avoids repetition of cases as for all the data in the given range the behave of the system will be same.divides the input data of a software unit into partitions of equivalent data from which test cases can be derived.
Boundary value analysis : This techniques is used to check the boundary values of the system. Boundary values means the behave of the software will change at these values. So there is maximum possibility of errors at boundaries.
Cause–effect graph : a cause–effect graph is a directed graph that maps a set of causes to a set of effects. The causes may be thought of as the input to the program, and the effects may be thought of as the output. Usually the graph shows the nodes representing the causes on the left side and the nodes representing the effects on the right side. There may be intermediate nodes in between that combine inputs using logical operators such as AND and OR. Its used basically in designing test cases based out of functionality.
Error guessing : error guessing is a test method in which test cases used to find bugs in programs are established based on experience in prior testing.The scope of test cases usually rely on the software tester involved, who uses past experience and intuition to determine what situations commonly cause software failure, or may cause errors to appear. Typical errors include divide by zero, null pointers, or invalid parameters.
Decision table testing : Its also a kind of Cause -effect technique where we create a decision based out of certain inputs. Each decision corresponds to a variable, relation or predicate whose possible values are listed among the condition alternatives. Each action is a procedure or operation to perform, and the entries specify whether (or in what order) the action is to be performed for the set of condition alternatives the entry corresponds to.
Types of Black Box Testing
There are many types of Black Box Testing but following are the prominent ones -
Functional testing - This black box testing type is related to functional requirements of a system; it is done by software testers.
Non-functional testing - This type of black box testing is not related to testing of a specific functionality , but non-functional requirements such as performance, scalability, usability.
Regression testing - Regression testing is done after code fixes , upgrades or any other system maintenance to check the new code has not affected the existing code.
No comments:
Post a Comment