Better test surface of mobile phone

Now mobile phone applications have entered the ordinary people's families, especially the use of smart phones can be said to have been common cover to enter each family. Learn the software, if you want to enter the field of mobile phone testing to develop, then you have to see if you master basic mobile phone testing knowledge. Here is a good set of mobile phone test surface questions, summed up to share to you:

1, what is the mobile phone software testing

The following tests are required for mobile phones as dedicated consumer electronics: Reliability Testing (RQT for Hardware, field trial for software), standard compliance testing (FTA), interoperability Testing (IOT), security testing (safety testing), strength testing, etc.

2. Performance test

Performance testing emphasizes the ability to perform certain operations over long periods of time, repetition, or strength to verify the performance of the product under various limit conditions. Performance testing is part of the system test in software testing, which tests the performance behavior of software running in an integrated system, and aims at early identification and elimination of architecture-related performance bottlenecks in software.

3. Performance test classification in mobile phone

(1) Time-dependent performance tests can be divided into long-stay tests and time-limited reaction tests

(2) Frequency-dependent performance testing is the ability of a test terminal to perform a function repeatedly and stably

(3) Concurrent testing is mainly the processing ability of testing terminal to perform multiple business simultaneously, such as simultaneous CS domain Voice service and PS domain download business, or the WWW Internet service at the same time as MP3 playback, in order to test the support capability of protocol stack, operating system and processor for concurrent business.

(4) The load test is mainly to verify the load capacity of the system. For example, multiple FTP downloads at the same time, so that downlink transmission rate close to the limit, to see if the terminal can work properly

4, the mobile phone performance test method

Mobile phone performance testing methods according to the degree of automation can be divided into manual testing and automated testing.

(1) Manual testing is mainly done manually by testers, and some monitoring instruments and tools are used to verify the performance of the mobile phone.

5, white box test, black box test

White-Box Testing (White-box testing, also known as logic-driven testing, structural testing) is the test object as an open box. When using the White-box test method for dynamic testing, it is necessary to test the internal structure and processing process of software products without testing the function of software products. White-Box testing is also known as structural testing and logic-driven testing.

Any Engineering product (note is any engineering product) can be tested using one of the following two methods.

Black box test: The functional design specifications of a known product can be tested to verify that each implemented function meets the requirements.

White Box testing: The internal working process of a known product can be tested to prove that each internal operation complies with the design specifications and that all internal components are inspected.

The black box test of the software means that the test should be done at the interface of the software. This method is to see the test object as a black box, the tester does not consider the internal logic structure and internal characteristics of the program, only according to the requirements of the program specification, check the function of the program is consistent with its function description. So black-box testing is also called functional testing or data-driven testing. The black box test is mainly to find the following types of errors:

1. Are there any features that are incorrect or missing?

2, on the interface, the input can be correctly accepted? Can I output the correct results?

3. Are there any data structure errors or external information (such as data file) access errors?

4, performance can meet the requirements?

5. Are there any initialization or termination errors?

The software's white-box test is a detailed examination of the procedural details of the software. This approach is to think of the test object as an open box, which allows the tester to design or select test Cases and test all the logical paths of the program, using the logical structure within the program and related information. Determine whether the actual state is consistent with the expected state by checking the program state at different points. So white-box testing is also known as structural testing or logic-driven testing. White box testing is mainly to the program module to check the following:

1, test all the independent execution path of the program module at least once.

2, to all the logical judgment, take "true" and take "false" two cases can be measured at least once.

3. The loop body is executed within the boundaries of the loop and the boundary of the operation.

4, test the effectiveness of internal data structure, and so on.

6. What is the test case?

7. How to write functional test cases in software testing

The source of the test, the need for testing

The main sources of test cases are:

1) Requirements description "and related documents

2) Related design instructions (summary design, detailed design, etc.)

3) communicate with the development team a record of requirements understanding (can be a developer's explanation)

4) Already basic form of UI (can be targeted to complement some use cases)

In short, all the project documents you can get are as much as possible. From the obtained data, we decompose some small "function points", understand "function points" and write the corresponding test cases.

A good test case should contain the following information:

1) name of the software or project

2) version of the Software or project (build number)

3) Function Module name

4) A simple description of the test case, that is, the purpose or method of the use case execution

5) Reference information for test cases (easy to track and reference)

6) Dependencies between this test case and other test cases

7) The preconditions for this use case, that is, the conditions that must be met to perform the use case, such as access to the database

8) Use Case number (ID), such as can be abbreviated software name-function block shorthand-no.

9) Step number, Operation procedure Description, test data description

10) Expected results (this is the most important) and actual results (if there is a bug management tool, this can be omitted)

11) Developers (must have) and testers (optional)

12) test Execution date

Better test surface of mobile phone