Remember just into the testing industry, did a big six months of app testing, time is not long, but also counted out a lot of pits, before there are a lot of notes to note, today turned out, and more up ...
Of course, the main is some functional points, notes, the specific operation of the process of what is not, I generally this kind of things are based on memory and experience drop ...
1. Security testing (permission)
1) Software permissions: including sending messages, making calls, linking networks, accessing mobile phone information, contact information, and so on.
2) data is stored, transmitted, etc. locally
3) input validation, authorization, data encryption, etc. that result from performing certain operations
4) Check based on various communication protocols or industry standards
2. Install and run the uninstall test
1) Verify that the app can install the shipment and unload, as well as the occupation of the system resources before and after the operation process and operation.
2) installation Run uninstall tips, reports, etc.
3) Check the installation path, whether the file is reasonable, whether the components are registered correctly, etc.
3. UI Test
1) User Interface (menu, dialog box, window) layout, whether the style to meet user needs, text location, description is correct, the interface aesthetic degree, text picture combination is reasonable
2) User-friendliness, humanization, ease of operation, etc.
4. Function test
1) Review requirements, various considerations, the internal external and non-functional direct indirect function points, compare requirements, extraction test points
2) According to some common analysis methods, equivalence class boundary value judgment Table causality diagram scene method and so on, design test cases, covering the extracted function points
3) test each phase of the continuous tracking of defects, do a good job of updating the use cases and constantly changing the needs of the business or the requirements of the error
5. Performance Test
1) Limit test: Verify the responsiveness of the app at various boundary conditions
such as: low battery, storage full. Weak nets and other conditions
2) Responsiveness Testing: Verify that different operations can meet user response needs in various situations
3) Stress test: The use of this resource in the system under repeated long-term operation
6. Interrupt test (interference)
For example: Before the background run to telephone, text messages, download files, listen to music to see the film and other performance under different circumstances
7. Compatibility test
1) different network environment (WiFi, 2G, 3G, 4G, etc.)
2) compatible with various equipment brand models and system versions
Apple, Android (different brands, different Android versions), etc.
8. Regression test
Regression test after bug fix, full regression before online delivery, verification
9. Upgrade and update test
Every time the app version iteration update, with different network environment, and different update permissions (force update, do not force the update), to download, install, update, start running and other tests
As the most recent work is based on web testing, some of the test points above are mainly based on functional testing, there should be omissions, if anyone sees, please say in the comment area, landlord at any time update ...
Some things about mobile app testing