Black Box Testing

What is Black Box Testing ?
Black box testing treats the software as a "black box" without any knowledge of internal implementation. black box testing methods are: equivalence partitioning, boundary value analysis, all pairs of testing, fuzz testing, model-based testing, traceability matrix, test and experimental tests based on specifications.

    test-based specifications: the specification based test designed to test the functionality of the software in accordance with applicable requirements.  Thus, items of data in the meter, and sees that the production of the test subject. This level of analysis typically requires an extended test cases to be supplied to the tester, which can then simply verify that a given input, the output value (or behavior), or "is" or "not" equal to expected value indicated in the test case.

    specification-based testing is necessary but not sufficient to avoid certain risks .

    Pros and Cons: The black box tester has no connection "with the code, and the perception of a tester is very simple: the code should contain some bugs. By using the principle:" Ask and you shall receive "black box tester in which programmers are not bugs. But the other part, the black box testing was said to be "like a walk in a dark labyrinth without a flashlight," because the testers do not know how the software tested was actually built. Therefore there are situations where (1) meter has written numerous test cases to verify something that could be tested by a single test and / or (2) back-end parts are not tested at all.
Therefore, black box testing has the advantage of a "Notice unaffiliated" on the one hand, and the disadvantage of "exploring the dark" on the other.