A mobile app testing basic ideas: Test Plan-Test program-Test case-execution: When the project hand, not immediately into the test work, but first familiar with the whole project process, the general framework over, do not understand the place to record, and then ask the development, the process is mastered, And then against the existing documents given to the project (Test Plan, test scheme), use cases do not have to write too detailed (the app module changes, too detailed maintenance costs too high, and the project manager gives you a short time, will waste the project execution time), each function module listed, the approximate function point, with what method to test , are labeled, and then perform the test according to the test requirements (at present, I use cases are only a summary of the implementation of the method, not specific details, change it convenient); Two mobile app test points: Functional testing
(Process test, Function point test), compatibility test, cross test, safety loading test (including application upgrade), stress test (interface pressure test), functional test: One by one test of specific function point, ensure that each point can correctly realize corresponding function; Compatibility test: Perform tests on mainstream device installation applications on the market Make sure that everything works; cross-testing: for applications that are running, if you enter SMS, phone and other software responses, the application will not be affected, and will ensure that the application works correctly; Install the uninstall test: Ensure that the application is properly installed, uninstalled, and can operate correctly (note the upgrade test of the application: the state before and after the upgrade); Stress testing: High user volume, highly interactive applications need to perform stress testing on the interface to ensure that it does not operate properly in the case of large user volume. Three things to note: Flash back (out of memory, etc.), on the phone, the probability of such problems appear very large, should focus on testing, for example, return access to a module (data from time to time to get the module), switching applications, repeated submissions, call interactions, etc. are the reasons for a large flash-back chance. (from 51 blogs)
"Software Testing" mobile software Testing
