Calabash-based client application demand-driven testing method

Abstract

The invention discloses a Calabash-based client application (APP) demand-driven testing method. The method comprises the steps that (A) a developed APP is obtained; (B) a script is updated, wherein atester checks whether it is needed to update a test script according to a demand and design document, if it is not needed, JenkinsJob is directly started to execute the test script, and otherwise a Calabash tool is opened to edit the test script; (C) JenkinsJob is started to execute the test script, wherein execution is performed according to the test script and scene configuration parameters; and(D) a test report is generated. According to the method, an automatic test mode is used to guarantee the quality of the client App in the process of quick development and version iterative upgrading,manpower cost in the testing process is lowered, test time is shortened, and test efficiency is improved.

Description

technical field [0001] The invention relates to a testing method for computer software development, in particular to a Calabash-based client application program requirement-driven testing method. Background technique [0002] Because traditional testing methods require testers to perform manually, usually black-box testing is performed, which is verified against requirements and design documents one by one, and then the test results are written into a test report, which is almost a pure manual workshop. This method lacks real User scenarios are easy to miss, lack of tracking and recording of the test process, and the actual task execution process cannot be reproduced. Bug management tools and test reports are not related, requiring secondary entry, which is inefficient; the other party’s App iteration speed is fast, usually once every two weeks. Updates, one version per month, and the client system is severely fragmented, with many devices, many brands, different versions, a...

AI Technical Summary

Problems solved by technology

[0002] Because traditional testing methods require testers to perform manually, usually black-box testing is performed, which is verified against requirements and design documents one by one, and then the test results are written into a test report, which is almost a pure manual workshop. This method lacks real User scenarios are easy to miss, lack of tracking and recording of the test process, and the actual task execution process cannot be reproduced. Bug management tools and test reports are not related, requiring secondary entry, which is inefficient; the other party’s App iteration speed is fast, usually once every two weeks. Updates, one version per month, and the client system is severely fragmented, with many devices, many brands, different versions, and inconsistent resolutions. It is difficult to conduct a comprehensive test on the App, and there is no guarantee of the quality of the App.

Images