手机测试相关英语.docxVIP

— PAGE \* Arabic 1 — 手机测试相关英语 Mobile Black Box Testing Introduction  Black box testing (black-box testing), also known as functional testing, data-driven testing or specification-based testing. When tested in this way, the program under test is treated as invisible inside the black box. Without any consideration the internal structure and internal features of the case, the test procedures were based only on functional requirements specification into account to determine the test cases and test results are correct inference. Thus black box testing is testing from the user point of view, the idea is intuitive since the black box program is required to do certain things, then we see if it is not in any case to do right. Complete any can not be verified, but also a set of black-box generated test cases for this approach to a limited test cases and more than enough to cover any. As the black box do not need to understand the internal structure, so many high-level tests such as the validation testing, system testing, acceptance testing are using black box testing.  The first is the usual black-box functional testing program. Requirements:  Each software features must be a test case or a recognized exception covered.  Data types and data values with the minimum set of tests.  With a series of real data types and data values to run the test overload, saturation, and other worst case results;  Using hypothetical data types and data values, testing the ability to exclude irregular input; Affect the performance of key modules, such as the basic algorithm, test unit performance (including accuracy, time, capacity, etc.).  Not only to assess whether the program made to do? But also examine whether the program should not do not do the 2 but also to examine the program in some other cases are normal. These include data types and data values of the exception, and so on. The following are several ways: (a) equivalence class partition, (b) cause and