Method and device for testing application program

Abstract

The invention discloses a method and a device for testing an application program, and relates to the technical field of computers. A specific embodiment of the method comprises the steps of formulating a version number of a to-be-tested version of an application program according to a test plan and a test function; testing clusters are deployed according to the types of the testing functions, and the testing clusters comprise a formal cluster and a gray scale cluster; and determining a target user corresponding to each version number through the shunting configuration, so that the target user accesses a corresponding test cluster according to the version number indicated by the shunting configuration to test a corresponding function. According to the embodiment, the test process is simplified, the test flexibility is improved, and the test cost is reduced.

Description

Technical field [0001] The present invention relates to the field of computer technology, and more particularly to a test method and apparatus for an application. Background technique [0002] The application version of the application can help the research team find problems through quick trials and correct issues in time before large-scale push users, greatly reduce a lot of risks. Making version tests not only meet some of the desires of people first experience, but also developing R & D teams that are not easy to discover, but also collect real user experiences, which are very helpful for optimizing new system content. [0003] In implementing the invention, the inventors have found that there is at least the following problems in the prior art: [0004] 1. Need to deploy multiple cluster environments, you can't support multiple versions of multiple versions simultaneously, and the test cost is high; [0005] 2. For testing based on version feature, the test system is too com...

AI Technical Summary

Problems solved by technology

[0004] 1. Multiple cluster environments need to be deployed, which cannot well support multiple versions to be tested at the same time, and the test cost is high;

[0005] 2. For testing based on version functional features, the test system is too complex and needs to be hard-coded to support multiple version branches for testing. The splitting logic of the test is coupled in the business, which has low flexibility and needs to be moved after the test is completed. In addition to the corresponding test code and shunt code

Images