Correct Answers to Objective Type Questions on Black Box Testing are at the end of this page:
Review your Skills on Black Box Testing-Through Descriptive Questions
Q. 1: Why we need to perform both types of testings like Functional as well as Structural Testing?
A functional (Black Box) test case might be taken from the documentation description of how to perform a certain function. For example, accepting the bar code input. On the other hand, a structural test case might be taken from a technical documentation manual.
Both methods together validate the entire system and is shown in Table below
Sr. | Test Phase | |||
Performed by Testers and |
Verification | Validation | ||
1 | Requirements Review | Developers, Users | X | |
2 | Unit Testing | Developers | X | |
3 | Integrated Testing | Developers | X | |
4 | System Testing | Developers, Users | X |
<<<<<< =================== >>>>>>
Q. 2: What is the source of knowledge for Functional Testing ?
The following items are the knowledge source of functional (or Black Box) testing
1) Requirements Document.
2) Specifications.
3) Domain knowledge.
4) Defect Analysis data.
<<<<<< =================== >>>>>>
Q. 3: What is Special Value Testing?
It is a soft of functional testing technique. It is most intuitive and least uniform. Special value testing occurs when a tester uses his or her domain knowledge, experience with similar programs and information about soft-spots (i.e., critical areas) to device test cases. It is also known as adhoc testing. It is tester’s ability dependent. Even though special value/adhoc testing is highly subjective, it often results in a set of test cases that is more effective in revealing faults than the test cases generated by other methods.
<<<<<< =================== >>>>>>
Q. 4: What is Random Testing?
Random testing is a testing technique in which instead of always choosing the min, min+, nom, max- and max values of a bounded variable, we use a random number generator to pick test case values. This will and biasing also during testing.
<<<<<< =================== >>>>>>
Q. 5: What are the differences between Static Testing and Dynamic Testing?
Sr. | Static Testing | Dynamic Testing |
1 | It talks about prevention. | It talks about cure. |
2 | It is more cost effective | It is less cost effective. |
3 | It may achieve 100% statement coverage. | It may achieve less than 50% statement coverage as it finds the errors only in the part of codes that are actually executed. |
4 | It is not time consuming. | It is time consuming as it may involve running several test cases. |
5 | It can be done before compilation. | It can be done only after executables are ready |
<<<<<< =================== >>>>>>
Q. 6: What are the advantages and disadvantages of functional test cases?
Functional test cases have two main advantages
1) They are independent of how the software is implemented. So, even if the implementation changes, the test cases are still useful.
2) Test case development can occur in parallel with the implementation, thereby reducing overall project development internal.
Functional test cases have two main disadvantages
1) Some unavoidable redundancies may exist among test cases.
2) There exists a possibility of gaps of untesting software.
Both of these problems can be solved if we combine the test cases, so obtained from both functional and structural testing.
<<<<<< =================== >>>>>>
Q. 7: What are the differences between Positive Testing and Negative Testing?
Sr. | Positive Testing | Negative Testing |
1 | Positive Testing tries to prove that a given product does what it is supposed to do. | Negative Testing is done to show that the product does not fail when an unexpected input is given. |
2 | A positive test case is one that verifies the requirements of the product with a set of expected output. | A negative test case will have the input values that may not have been represented in the SRS. These are unknown conditions for the product. |
3 | The purpose of positive testing is to prove that the product works as per the user specifications. | The purpose of negative testing is to try and break the system. |
4 | Positive testing checks the product’s behaviour. | Negative testing covers scenarios for which the product is not designed and coded. |
5 | Positive testing is done to verify the known test conditions. | Negative testing is done to break the product with unknown test conditions i.e., test conditions that lie outside SRS. |
6 | If all documented requirements and test conditions are covered then it gives 100% coverage.
For example: A product delivering an error when it is expected to give error. |
There is no end to negative testing and 100% coverage is impractical here.
For example: A product not delivering an error when it should or delivering an error when it should not. |
<<<<<< =================== >>>>>>
Q. 8: What is Domain Testing?
Domain testing is a sort of testing strategy wherein we do not look even at SRS of a software product but test purely on the basis of domain knowledge and expertise in the domain of application.
For example, in some banking software, knowing the account opening, closing etc. processes, enables a tester to test that functionality better.
<<<<<< =================== >>>>>>
Q. 9: What is Documentation Testing?
Documentation testing is a testing done to ensure that the documentation is consistent with the product.
<<<<<< =================== >>>>>>
Q. 10: What are the characteristics of a good test?
1) A good test has a high probability of finding an error.
2) A good test is not redundant.
3) A good test is the “best of breed”.
4) A good test should be neither too simple nor too complex.
Go Back to Objective Type Questions Page
Many More Articles & Tutorials on Black Box Testing
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.
This wbeiste makes things hella easy.
Keep these atrclies coming as they\’ve opened many new doors for me.