What is Black Box Testing?
Black Box Testing is done by Testing team they will look into a user interface part of the application.They are not exposed logic of code or flow of code.Black box testing is done after white box testing.Black box testing helps for functionality verification.It has certain characteristics:
4.Decision Tables
Black Box Testing is done by Testing team they will look into a user interface part of the application.They are not exposed logic of code or flow of code.Black box testing is done after white box testing.Black box testing helps for functionality verification.It has certain characteristics:
![]() |
What is Black Box Testing? |
- It helps in identifying the incomplete,inconsistency requirement based on the requirement they find any issues involved when the system is tested as a complete entity.
- Not all the requirements are stated as explicitly.
- It will check the overall functionality.
- It will test by valid number of inputs and outputs.
The various techniques are involved to do Black box testing they are:
- Requirement Based testing
- Positive and negative testing
- Boundary value analysis
- Decision tables
- Equivalence partitioning
- State based testing
- Compatibility testing
- User documentation testing
- domain testing.
1.Requirement Based Testing
- It is used to validate the requirement based on the system requirement specification.Not all the requirements are explicitly sated but the documented as part of the requirement specification, some of the requirements are implicitly stated but that are nor documented.
- All explicit and implicit requirements are collected and documented as Test requirement Specification.
- The requirements are tracked by Requirement Traceability Matrix.RTM is used to ensure that each and every requirement has a mininum one testcase or not.
2.Positive and Negative Testing
- In Positive testing they check the application by giving a valid inputs is know as positive testing.It mostly used to verify the application with know test conditions.
- In negative testing they check the application by providing a invalid inputs is know as negative testing.It mostly used to break the product with unknow input.
3.Boundary Value Analysis
- Boundary value analysis can be done only for range of values.Boundary value analysis is useful to create a test cases when the input data is made up of clearly identifiable boundaries.
- We cannot use the concept of Equivalence partitioning.
- A decision table is applicable only when input and output information can be demonstrate as boolean condition TRUE or FALSE.They have several steps to form decision table are as follows:
- First we need to identify the decision variables and possible values for decision variables.
- They will list the combination of allowed values of each of the variables.
- Their is not that much important for a given combination of other input variables then they assigned as don't care symbol.
5.Equivalence Partitioning
- Equivalence Partitioning can be done for set of values,range of values and boolean of values.We use the concept of Boundary value analysis in equivalence partitioning.It is useful to minimize the number of test cases when input data can be divided into distinct set.
6.State Based Testing or Graph Based Testing
- State Based Testing is used to test the language translator,workflow transaction and data flow.
7. Compatibility Testing
- Testing the application in different hardware and software environment is called as Compatibility Testing.The difference between the compatibility issue and functionality issues is if all the software is not working with all platform is called as functionality issue.If software is working with one or few platforms is called as compatibility issue.It classified into two types:
- Backward Compatibility testing
- forward Compatibility Testing
8.User Documentation Testing
- User documentation testing is used to test whether the documentation matches the product or not.
- It has two objectives that are:
- They check whatever we coated in the document that available in the product or not.
- They will check the product is explained correctly in the document.
9. Domain Testing
- Domain testing is the ability to design and execute test cases that relete to people who will buy and use the product.
0 comments:
Post a Comment