As the saying goes, "You live and learn a lesson", which used to be no better grasp on the progress of the test in APP test cycle.
The project brief case, APP testing software development project where the author follows the waterfall model, the project includes android and iOS, with one month basic iteration cycle. Human testing distribution, coupled with the implementation of management, a total of two, functional tests do have to do the automation section.
One might doubt that one month period, compared to Agile, iterative cycle or week is concerned, not a lot of it easily? Yes, the app a month, can not be considered quickly released, but the author of the project, namely android / iOS version, a total of 4 models app, the average app, on a week's worth of iterative development cycle.
Therefore, it is particularly important to grasp the progress of the test.
Considering the android and iOS app business processes and logic is the same, developers are usually sent to test the version submitted at the same time, to grasp the progress of the test from the following aspects.
A. Manual testing can not be less
Time to send test versions, in addition to looking to determine the scope of the development, those that are explicitly testing purposes, faster start earlier testing is necessary. Use smoke testing method, ran through the entire process, timely feedback functionality bug students to develop as much as possible so that progress can continue the progress of the test.
Second, when to intervene scripting
In the previous two editions sent to test, I began to write the script, spent a lot of time, affect nearly functional test, when the release of stored pages found an error occurred. After stretched twice this case, send test versions when using the first manual functional testing, after running through the main processes in the development of the students countless bug submerged in the clouds, this time to start the handwriting automation use cases.
two. Select which automated regression testing
In manual testing, understanding the basic functions, the flexibility to choose the number of reproducible, simple logic, eye-consuming, by the function of the smoke test of the module selection UI Automation testing. Probably a small version of iterations, with two days basically can handle that.
Three automation purposes
The purpose of automation is to automate some of the manual testing, repeat the liberation of the human brain, and can devote more energy to the complex business logic test work.
In order to reduce non-automated and manual testing, since this can cause missed opportunity functional testing, project delays release time, this lesson is thought-provoking.