Mobile phone black box testing details

1. Release Test
Purpose:
Test whether the basic functions of mobile phones are implemented and whether further testing is necessary
 
Attention:
The test case of N release test is typical and mainly reflects the test case of the most basic functions of mobile phones.
N this type of test only needs to be tested based on test case, and does not need to be further used.
N if an error unrelated to case is found, the error report can be filled in only after the test is passed.
N this type of test has a threshold value, that is, the pass rate of test case reaches a certain value (such as 95%) to announce the successful release of the version and start further testing. Otherwise, this version is invalid.
N in addition to the threshold value, this version will be terminated if the test case of an important functional module fails.
2 system test
Full Round System Test
N Purpose
U comprehensively tests all functions of the mobile phone (all language packs)
U because case cannot contain all aspects, make proper use of the test and try your best to complete the test.
Common system test (medium or minor)
 
Attention:
N system test is generally divided into two parts: "run case" and free test.
N at the initial stage of the test, you generally only need to test according to test case to record some non-reproducible errors. If the test case problem is encountered or is insufficient, it should be resolved immediately (discussed with the team leader or special list and supplemented with the test case ). After the end of this stage, a summary report is generally written. Write the test results, problems, and opinions of this stage in English ).
N when all test cases are tested, the free test period begins. The free test here has a clear purpose and scope. In general, free test only needs to test the module in charge of this period of time. Free test is also responsible for recreating the "running case" in the early stage, which is a legacy error that cannot be reproduced.
2.5.3 focus Test
Purpose:
N is concentrated on one or several points for testing (same as system test)
 
2.5.4 stress test
Purpose:
N targeted strength tests to solve major errors found in the market
N is mainly used for edge testing (critical testing ).
 
Attention:
N stress testing, as the name implies, puts some pressure on the mobile phone to find out the error on the mobile phone software. Generally, the pressure on mobile phones is:
U Storage pressure: Because mobile phones use stack-based storage, when a storage block is full, if the programmer does not handle it or the processing is poor, it is easy to cause other storage areas to be erased, and problems may occur on the UI (other functions cannot be used normally ).
U boundary pressure: boundary is always the easiest place for programmers to ignore.
U response pressure: Sometimes an operation may take a long time to process. During the process, if the tester continues to perform other operations, the problem may occur.
U network traffic pressure (such as text message service when answering the phone) and so on.
N in projects, stress test is sometimes used to reproduce non-reproducible errors.
N because many non-reproducible errors are caused by memory leak (Memory leakage), it is a good way to repeatedly repeat the same operation to reproduce an non-reproducible error.
2.5.5 free test
Purpose:
N errors that are not completed in system test cannot be reproduced.
N. Find the ignored error that is not found at ordinary times.
Attention:
N the free test used in the system test stage has obvious purpose and scope.
N in theory, the free test should exhaust all testing methods for the tested range. However, this is unrealistic. In actual projects, there are two main aspects that need to be paid attention to by free test.
U 1 is inspired by the UI spec. The test case should be written based on the UI spec, So breaking through the UI spec is an effective method. Ui spec has a certain depth of exploration. Increasing the depth of exploration is a breakthrough. In addition, implementing the same function in different ways is also a breakthrough.
U second, focus on the interaction between different feature. This is where mobile phone software is relatively prone to problems, and test case is rarely reflected. This is a huge free test space.