1. test: should be divided into test version and online version
1) Beta: The requirements document prototype drawing, the UI diagrams, use cases for covering UI (style, layout, copy, etc.), functions, scenes and other (invisibility point and scene requirements document not described, other languages, other machines compatibility testing)
2) online edition: All the positive processes, testing boundary values (related to the amount and other important functions), and configuration of the test environment inconsistent functional tests.
The purpose is to: ensure the normal operation of the user can be normal.
2. Functional Testing:
1) limiting the number of functions have to be on the final test. Such as password six times, you can log normal after 24h;
2) to test the process forward, and then test after the other cases go through. Similar to the smoke test;
3) test data to be ready ahead of time, try to use as many of the least functional test coverage data and test scenarios;
4) as much as possible to design some test scenarios, to prevent abnormal operation;
5) UI consistency is also tested. For example, the same style, layout and copywriting, etc.
