Mobile app testing process and methods?

1. First is the confirmation and preparation of test resources

(1) Product requirements documents, product prototype diagrams, interface description documents and design description documents should be complete;

(2) Preparation of test equipment and tools: real machines of different versions of IOS and andriod, as well as preparation of related test tools.

2. Design and review of test cases

(1) Design general functional test cases for the client based on product requirements documents, product prototype diagrams and other documents;

(2) Test case review, modification and improvement. After passing the review, the formal testing phase will begin.

3. UI testing

(1) Ensure that the prototypes and renderings on hand are the latest versions and meet the requirements of product managers and users;

(2) ) During the testing process, everything is based on the renderings. If you have any suggestions on user experience, you can first confirm with the product manager by email. After the confirmation is passed, you can formally raise user experience issues to the development;

(3) Since the data in the test environment is simulated data, the data types that may appear in the formal environment must be considered in advance during testing.

4. Functional testing

(1) During functional testing, the software functions are traversed mainly based on the written functional test cases;

(2) Involved tests It mainly includes basic function testing, installation, uninstallation, operation testing, and exception handling (including handling of abnormal situations such as sudden network disconnection or slow network speed, insufficient machine memory, etc.) testing.

5. Interruption test

(1) When the software is running, answer calls, receive text messages, lock the screen, alarm, charge, and use the software after receiving notification reminders. The software should It can still be used normally;

(2) When the software is running, it should be switched from the foreground to the background, and then switched back to the foreground, it should still be able to be used normally.

6. Compatibility and adaptation test

(1) Hardware adaptation: adaptation of different mobile phone manufacturers, hardware performance, and different screen sizes;

(2) OS version compatibility: IOS6-9; Android3 and above, etc. If some new APIs are used that are not supported on the old system, it will cause a crash;

(3) Different resolution screens Adaptation: Mobile devices have various resolutions. If the app does not perform appropriate processing, it may display poorly or even affect the operation of functions.

(4) Compatibility testing must be conducted on a certain number of real machines. Since there are too many types of real machines, especially Android, when doing compatibility testing, you can select several typical real machines that are widely used. , conduct compatibility testing;

(5) In addition, you can use the open source test testin cloud test to conduct compatibility tests on more models. testin cloud test provides basic operating conditions and some screenshots, as well as simple Test reports help expand the scope of testing.

7. Performance test

(1) Client performance test focuses on: installation and uninstallation time, startup time, page loading time, CPU, memory, traffic, consumption occupied by main functions Battery, etc., and whether it has any advantages compared with similar products;

(2) The page loading time can be obtained by using the Android debugging tool DDMS. Search the Displayed keyword in DDMS to see the page loading. Time;

(3) The CPU, memory, traffic, etc. occupied by the main functions during operation can be obtained with the open source tool emmagee (for Android);

(4) As for the server For the performance of the terminal, the interface is mainly used to put pressure on the server, focusing on response time, throughput, number of concurrencies, transaction pass rate, etc. It can be tested with the same tools as loadrunner and jmeter.

8. Stability test

(1) The stability of Android APP is often tested using the monkey command, which simulates human operations through a random event stream to check the program's memory overflow, Null pointers are very useful.

(2) Monkey is mainly used to detect system ANR and Crash problems

9. Test analysis and test report output

After the above tests are completed, A complete analysis and report document (including buglist, performance and stability result analysis, version launch risk analysis, etc.) should be formed and output to all relevant personnel