What are the steps to test the software function of the whole mobile phone?

1. Take the MIUI system as an example, open the main page of the MIUI system settings app, and click the "My Device" option at the top of the page;

2. After opening the My Device page, click the "All Parameters" menu item;

3. In the all parameters page, find the "Kernel Version" option, and click the option continuously, that is, the shed can enter the mobile phone function test page;

4. In the open mobile phone function settings page, click to select the function item to be tested in the chain;

5. Finally, in the open functional test page, test each function in turn, and if you can pass, click the "Pass" button; If the test fails, click the "Fail" button.

1. Need to shout and analyze the stage: read the demand, understand the demand, analyze the demand point, and participate in the demand review meeting.

2. Test plan stage: The main task is to write the test plan, refer to the software requirements specification, the overall project plan, including the test scope, schedule, manpower and material resource allocation, and the formulation of the overall test strategy.

3. Write test cases.

Properly understand the design, build a test case framework, and write test cases according to the requirements and design.

4. Test execution stage: build the environment to prepare the data, execute the first test and then enter the formal test (system test, regression test.

cross-testing, free testing), bug management until the end of the test.

5. Output test report.

Output a test report to check whether it can be launched.

1. Demand analysis stage: read the requirements, understand the needs, analyze the needs points, and participate in the needs review meeting.

3. Write test cases: properly understand the design, build the test case framework, and write test cases according to the requirements and design.

4. Test execution stage: build an environment to prepare data, execute the first test and then enter the formal test (system test, regression test, cross test, free test), and manage the bug until the end of the test.

5. Output test report: Output test report to confirm whether it can be launched.

Mobile phone software testing and computer software testing will basically be the same, compared with computer software, mobile phone software testing is relatively simple program. Here are a few of the key points that I have summarized.

1.Requirements review (whether it is reasonable, whether it is consistent with the design) 2Test plan (who to test, test tools, time to test)3Test design (the use case design of the test is the most important).

4.Conduct the test, record the test information (test at the point)5Test report (submit test problems, bugs, design discrepancies, etc.) 6Track the issue (whether the issue has been resolved or not).

7.Release the product (regression testing).

8.Test summary.

If you are still not sure, you can take a look at the flowchart and understand the principle of testing first.

1. The first is to confirm and prepare test resources.

2. Design and review of test cases.

3. UI test.

4. Functional testing.

5. Interrupt the test.

6. Compatibility and adaptation test.

7. Performance test.

8. Stability test.

9. Test analysis and test report output.

Follow the requirements, write the use cases when the requirements come, and do the tests after the development is completed.

It depends on what kind of test, there are system tests, integration tests, and so on.

1. Analysis of test requirements;

2. Write test plans or test cases;

3. Set up the test environment, prepare the test data and test execution;

4. Test feedback refers to the process of finding abnormalities during the testing process, conducting defect analysis to determine the throne, and then corresponding with relevant developers, and finally promoting the problem to be solved;

5. Summary and analysis after the end of the test project;

6. Regression testing, after all tests are completed, must be carried out before the version is submitted.

1. Equivalence class analysis.

The equivalence class division method can be roughly divided into several categories for the state of the mobile phone:

1.Keys (equivalence method): valid input and invalid input (valid input refers to um and menu indication; Invalid input refers to keys and user actions that are not defined at this time for the test menu function);

2.External Interrupt Class (Equivalence Method): Common, Incommon, and Inactive.

Commonly used: incoming calls and messages (SMS, color letters, push messages); Flip-close lid; side buttons; Headset FM; Scenario mode; The battery is low.

Not Commonly Used: Charging; Alarm clock, notepad, shutdown time, hour time signal; icon animated display; icon animation refresh; The interface pop display box input is empty or full; Font dismantling and balance interface pop display box status input method default character encoding default; Invalid SIM card; Compatible with large capacity and other SIM cards; Sort; Number identification of the royal attendant;

2. Boundary value analysis.

Example 1: Equivalence class division method for short message sending function:

3. Wrong guessing method.

Example 1: Use the example of a mobile phone alarm clock to introduce the basic concept of the false guess method and explain the meaning of the wrong guess method.

29 missed calls, the planned partition allocation in memory has been occupied. Even the same number is also resource-intensive. Assuming that the 30th call** happens to be the caller ID is not displayed at this time, that is, when the caller ID is unknown or the caller ID is hidden abroad (the caller ID hiding function is automatically turned on when foreign countries protect personal privacy and automatically turn on the caller ID hiding function), there may be a bug, and the actual situation proves that there will be a reset problem at this time.