CN111427795A - Code test control method and device, storage medium and electronic equipment - Google Patents
Code test control method and device, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111427795A CN111427795A CN202010279147.4A CN202010279147A CN111427795A CN 111427795 A CN111427795 A CN 111427795A CN 202010279147 A CN202010279147 A CN 202010279147A CN 111427795 A CN111427795 A CN 111427795A
- Authority
- CN
- China
- Prior art keywords
- tested
- test
- code
- requirement
- test terminal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure belongs to the technical field of computers, and relates to a code test control method and device, a storage medium and electronic equipment. The method comprises the following steps: acquiring a target test requirement; determining a first code branch to be tested according to the target test requirement; determining a first application package to be tested according to the first code branch to be tested; and sending the first application program package to be tested to the test terminal. According to the method and the device, a target test requirement is obtained, a first code branch to be tested is determined according to the target test requirement, a first application package to be tested is determined according to the first code branch to be tested, and the first application package to be tested is sent to a test terminal. The program package corresponding to the code branch to be tested can be pushed and automatically installed on the test terminal of the tester, so that the error condition caused by manual operation is avoided, the interaction times between the tester and the developer can be reduced, and the test efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a code test control method and a code test control apparatus, a computer-readable storage medium, and an electronic device.
Background
At present, software developers can separate out a plurality of android application packages in the process of needing to test and repair bugs, and testers need to download and install the android application packages for requirement testing and feed test results back to the developers.
In the process, a tester can continuously repeat three actions of searching the bag body, downloading the bag body and installing the bag body according to the single number, so that the conditions of finding a wrong bag body, downloading the wrong bag body and installing the wrong bag body are easy to occur, the test version is inconsistent with the test-promoting version, and the code test efficiency is reduced due to a large amount of repeated operations.
In view of the above, there is a need in the art to develop a new code test control method and apparatus.
It is to be noted that the information disclosed in the above background section is only for enhancement of understanding of the background of the present disclosure, and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
An object of the present disclosure is to provide a code test control method, a code test control apparatus, a computer-readable storage medium, and an electronic device, which overcome, at least to some extent, problems of low test accuracy, time consumption, and the like due to limitations of related art.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to an aspect of the present disclosure, there is provided a code test control method, the method including: acquiring a target test requirement; determining a first code branch to be tested according to the target test requirement; determining a first application program package to be tested according to the first code branch to be tested; and sending the first application program package to be tested to a test terminal.
In an exemplary embodiment of the present disclosure, the method further comprises: the sending the first application package to be tested to a test terminal comprises: and sending the first application program package to be tested to the test terminal, and automatically installing the first application program package on the test terminal.
In an exemplary embodiment of the present disclosure, sending the first application package to be tested to the test terminal, and automatically installing the first application package on the test terminal includes: and sending the first application package to be tested to the test terminal, triggering the test terminal to automatically install the first application package to be tested, and prompting the test terminal to test the first application package to be tested after the installation is finished.
In an exemplary embodiment of the disclosure, the sending the first application package to be tested to a test terminal includes: and determining a target test terminal according to the target test requirement, and sending the first application program package to be tested to the target test terminal.
In an exemplary embodiment of the present disclosure, the target test requirement includes a requirement identifier, and the target test terminal is a terminal that inputs the requirement identifier.
In an exemplary embodiment of the disclosure, the test terminal inputs the requirement identifier by typing or scanning.
In an exemplary embodiment of the present disclosure, the method further comprises: receiving a test result fed back by the test terminal; if the test result is that the test is not passed, determining a second code branch to be tested, wherein the second code branch to be tested is a code branch to be tested obtained by repairing the first code branch to be tested; automatically generating a second application program package to be tested according to the second code branch to be tested; and sending the second application program package to be tested to a test terminal.
In an exemplary embodiment of the present disclosure, the method further comprises: and if the test result is that the test is passed, indicating the code warehouse to merge the first code branch to be tested into the main code.
In an exemplary embodiment of the disclosure, the determining the second code branch under test includes: judging whether the first code branch to be tested is updated; and if so, determining the updated first code branch to be tested as a second code branch to be tested.
In an exemplary embodiment of the present disclosure, the method further comprises: the sending the second application package to be tested to a test terminal includes: and sending the second application program package to be tested to the test terminal, and automatically installing the second application program package on the test terminal.
In an exemplary embodiment of the present disclosure, the sending the second application package to be tested to the test terminal, and automatically installing the second application package to be tested on the test terminal includes: and sending the second application program package to be tested to the test terminal, triggering the test terminal to automatically install the second application program package to be tested, and prompting the test terminal to test the second application program package to be tested after the installation is finished.
In an exemplary embodiment of the present disclosure, the target test requirement comprises a requirement identification; the determining a first code branch to be tested according to the test requirement includes: and determining a first code branch to be tested according to the requirement identification.
In an exemplary embodiment of the disclosure, before the determining the first to-be-tested code branch according to the test requirement, the method further includes: establishing a mapping relation between a first code branch to be tested and a requirement identifier; the determining as the first code branch to be tested according to the requirement identification comprises: and determining the code branch to be tested corresponding to the requirement identification as a first code branch to be tested according to the mapping relation.
In an exemplary embodiment of the disclosure, the first to-be-tested application package is generated by automatically packaging according to the first to-be-tested code branch before the target test requirement is obtained.
In an exemplary embodiment of the present disclosure, the application package includes: android application packages.
According to an aspect of the present disclosure, there is provided an electronic device including: a processor and a memory; wherein the memory has stored thereon computer readable instructions which, when executed by the processor, implement the code test control method of any of the above exemplary embodiments.
According to an aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the code test control method in any of the above-described exemplary embodiments.
As can be seen from the foregoing technical solutions, the code test control method, the code test control apparatus, the computer storage medium and the electronic device in the exemplary embodiments of the present disclosure have at least the following advantages and positive effects:
in the methods and apparatus provided by the exemplary embodiments of the present disclosure,
the method comprises the steps of obtaining a target test requirement, determining a first code branch to be tested according to the target test requirement, determining a first application package to be tested according to the first code branch to be tested, and sending the first application package to be tested to a test terminal. The program package corresponding to the code branch to be tested can be pushed and automatically installed on the test terminal of the tester, so that the error condition caused by manual operation is avoided, the interaction times between the tester and the developer can be reduced, and the test efficiency is improved.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.
FIG. 1 schematically illustrates a flow chart of a code test control method in an exemplary embodiment of the present disclosure;
FIG. 2 is a flow chart diagram schematically illustrating a processing method after receiving a test result in an exemplary embodiment of the disclosure;
FIG. 3 is a schematic flow chart diagram illustrating a method for determining a second code branch under test in an exemplary embodiment of the present disclosure;
FIG. 4 schematically illustrates an electronic device for implementing a code test control method in an exemplary embodiment of the present disclosure;
fig. 5 schematically illustrates a computer-readable storage medium for implementing a code test control method in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
The terms "a," "an," "the," and "said" are used in this specification to denote the presence of one or more elements/components/parts/etc.; the terms "comprising" and "having" are intended to be inclusive and mean that there may be additional elements/components/etc. other than the listed elements/components/etc.; the terms "first" and "second", etc. are used merely as labels, and are not limiting on the number of their objects.
Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities.
In view of the problems in the related art, the present disclosure provides a code test control method. Fig. 1 shows a flow chart of a code test control method, and it should be noted that although a logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in an order different from that shown or described herein.
As shown in fig. 1, the code test control method at least includes the following steps:
and S110, acquiring a target test requirement.
And S120, determining a first code branch to be tested according to the target test requirement.
And S130, determining a first application program package to be tested according to the first code branch to be tested.
And S140, sending the first application program package to be tested to the test terminal.
In an exemplary embodiment of the disclosure, a target test requirement is obtained, a first code branch to be tested is determined according to the target test requirement, a first application package to be tested is determined according to the first code branch to be tested, and the first application package to be tested is sent to a test terminal. The program package corresponding to the code branch to be tested can be pushed and automatically installed on the test terminal of the tester, so that the error condition caused by manual operation is avoided, the interaction times between the tester and the developer can be reduced, and the test efficiency is improved.
The respective steps of the code test control method will be described in detail below.
In step S110, a target test requirement is acquired.
In the exemplary embodiment of the disclosure, when a developer develops an application, the development is performed according to a plurality of cycles, each cycle generates a new version of the installation package, and a requirement is newly added in each cycle. Therefore, the target test request may be issued by a tester or by a tester, and the present exemplary embodiment is not particularly limited thereto.
In step S120, a first code branch under test is determined according to the target test requirement.
In an exemplary embodiment of the present disclosure, the first code branch to be tested may be further determined according to the acquired target test requirement.
In an alternative embodiment, the target test requirement includes a requirement identifier, and the first code branch to be tested may be determined according to the requirement identifier. In order to distinguish the target test requirements subsequently, the requirements can be distinguished according to the requirement identification in the target test requirements. Therefore, each target test requirement corresponds to a unique requirement identifier. The first code branch under test may be further determined according to the requirement identification.
In an optional embodiment, a mapping relationship between the code branch to be tested and the requirement identifier is established. And determining the code branch to be tested corresponding to the requirement identification as a first code branch to be tested according to the mapping relation. The code branch under test may be a code branch that is newly developed and to be tested. The code branch is newly built, so that the requirement of testing on the code branch can be met, and the integrity and the availability of the mainline code are ensured.
A mapping relationship is established between the code branch to be tested and the requirement identifier, where the mapping relationship may be one-to-one, one-to-many, many-to-one, or many-to-many, and this exemplary embodiment is not particularly limited in this respect. When the mapping relation and the requirement identification are determined, the corresponding code branch to be tested, namely the first code branch to be tested, can be determined through the mapping relation and the requirement identification.
In step S130, a first to-be-tested application package is determined according to the first to-be-tested code branch.
In an exemplary embodiment of the present disclosure, after determining the first code division to be tested, the application package to be tested may be further determined.
In an alternative embodiment, the first to-be-tested application package is generated by automatically packaging according to the first to-be-tested code branch before the target test requirement is acquired. The first application package to be tested may be any application package, which is not particularly limited in this exemplary embodiment.
In an alternative embodiment, the first to-be-tested application package comprises an android application package. The Android Application Package (APK) is an application package file format used by an Android operating system, and is used for distributing and installing mobile and middleware. The code of an android application program is required to be run on an android device, the android application program must be compiled and then packaged into a file which can be identified by an android system to be run, and the file format which can be identified and run by the android system is an android application program package.
Specifically, the operation of automatically packaging the first to-be-tested code branch may be implemented by a packaging server. The packaging server is used for generating a new version of APK installation package by packaging codes developed by developers aiming at application programs.
In step S140, the first application package to be tested is sent to the test terminal.
In an exemplary embodiment of the present disclosure, the test terminal may be a terminal device specially used for code testing, and a tester uses the test terminal to test the application package.
In an optional embodiment, the test terminal is determined according to the target test requirement, and the first application package to be tested is sent to the test terminal. To implement the functionality of the test code, a plurality of test terminals may be provided from which one or more test terminals are selected for testing.
In particular, one or more test terminals may be determined by the target test requirements.
In an alternative embodiment, the target test requirement includes a requirement identifier, and the test terminal is a terminal for inputting the requirement identifier. In order to distinguish the target test requirements subsequently, the requirements can be distinguished according to the requirement identification in the target test requirements. Therefore, each target test requirement corresponds to a unique requirement identifier. The test terminal can be further determined according to the requirement identification.
In an alternative embodiment, the test terminal inputs the requirement identification by typing or scanning. The test terminal can provide two modes of binding the requirement identification, namely inputting the corresponding requirement identification and scanning the requirement identification. For example, the requirement identifier may be composed of numbers, letters and symbols, and may be bound by typing; when the requirement identifier is in the form of a two-dimensional code, the requirement identifier can be bound in a scanning mode. The requirement identifier may be in other forms, and the exemplary embodiment is not particularly limited to this.
In the exemplary embodiment, the test terminal is determined according to the target test requirement, so that the automation degree of code test is improved, and a tester can determine the test terminal more conveniently.
After determining the test terminal, a manner of sending the first to-be-tested application package to the test terminal may be further determined.
In an alternative embodiment, the first application package to be tested is sent to the test terminal and automatically installed on the test terminal. Specifically, according to the automatic integration system, after the first application package to be tested is sent to the test terminal, the first application package to be tested can be directly installed on the test terminal.
In the exemplary embodiment, a tester does not need to manually search, download and install the first application package to be tested, after the target test requirement is obtained, the first application package to be tested, in which the first code branch to be tested corresponding to the target test requirement is packaged, can be intelligently pushed to the test terminal, and the test terminal is triggered to automatically install the first application package to be tested, so that the tester can timely and effectively test the code to be tested, and the code test efficiency is improved.
In an optional embodiment, the first application package to be tested is sent to the test terminal, the test terminal is triggered to automatically install the first application package to be tested, and the test terminal is prompted to test the first application package to be tested after the installation is finished. The automated installation of the first to-be-tested installation package may be performed by the test terminal. Therefore, when the first application package to be tested is received, the test terminal is triggered to automatically install the first application package to be tested.
In order to improve the automation program of the code test, prompt information can be displayed after the installation is finished so as to prompt developers to finish the installation, and the code test operation can be further carried out.
After the test, further operations may be performed based on the obtained test results.
In an alternative embodiment, fig. 2 shows a flowchart of a processing method after receiving a test result, and as shown in fig. 2, the method at least includes the following steps: in step S210, a test result fed back by the test terminal is received. After the test terminal tests the first application package to be tested, the corresponding test result can be determined and fed back to the tester in time, so that the tester can perform secondary processing conveniently.
In step S220, if the test result is that the test fails, a second code branch to be tested is determined, where the second code branch to be tested is a code branch to be tested obtained by repairing the first code branch to be tested. When the test result of the first application package to be tested is determined to be failed, the developer can repair the corresponding part in the first code branch to be tested, and determine the repaired first code branch as the second code branch.
In an alternative embodiment, fig. 3 is a schematic flowchart of a method for determining a second code branch to be tested, where as shown in fig. 3, the method at least includes the following steps: in step S310, it is determined whether the first branch of code under test is updated. For example, the repair and update results of the first branch of code under test may be detected in real time or at equal intervals.
In step S320, if yes, the updated first code branch to be tested is determined as the second code branch to be tested. And when the first code branch to be tested is received to be repaired and the updating is completed, further determining that the repaired first code branch to be tested is the second code branch to be tested.
In the exemplary embodiment, the repaired first code branch to be tested is determined as a second code branch to be tested, and a tester can perform subsequent tests on the second code branch to be tested.
In step S230, a second application package under test is automatically generated according to the second code branch under test. The second application package under test may be generated by automatic packaging according to the second code branch under test. Specifically, the operation of automatically packaging the second code branch to be tested may be implemented by the packaging server. The packaging server is used for generating a new version of APK installation package by packaging codes developed by developers aiming at application programs.
In step S240, the second application package to be tested is sent to the test terminal.
In this example embodiment, when the test fails, whether the branch of the code to be tested having the bug is repaired or not is continuously monitored, and when the branch of the code to be tested is repaired, the repaired branch of the code to be tested is packaged and pushed to the test terminal of the tester. Therefore, when the test fails, the tester only needs to wait for the test terminal to receive the repaired progeny code branch and then perform the secondary test, the interaction times between the tester and the developer are reduced, and the process of searching, downloading and installing the application program package is reduced.
In an optional embodiment, the second application package to be tested is sent to the test terminal and automatically installed on the test terminal. Specifically, according to the automatic integration system, after the second application package to be tested is sent to the test terminal, the second application package to be tested can be directly installed on the test terminal.
In an optional embodiment, the second application package to be tested is sent to the test terminal, the test terminal is triggered to automatically report the second application package to be tested, and the test terminal is prompted to test the second application package to be tested after the installation is finished. The automated installation of the second installation package under test may be performed by the test terminal. Therefore, when the second application package to be tested is received, the test terminal is triggered to automatically install the second application package to be tested.
In order to improve the automation program of the code test, prompt information can be displayed after the installation is finished so as to prompt developers to finish the installation, and secondary code test operation can be carried out.
In addition to performing secondary processing when the test result is failed, further processing may be performed when the test result is passed.
In an alternative embodiment, if the test result is that the test passes, the code repository is prompted to merge the first branch of code to be tested into the main code. The main code stored in the code repository has stable code and can be used directly for distribution. When the test result is passed, it may be determined that the function to be implemented by the first test code branch is implemented and available for release. Therefore, the developer can be prompted to carry out the operation of merging the first code branch to be tested into the main code so as to complete the function of the main code.
It should be noted that although the above exemplary embodiment implementations describe the various steps of the method in the present disclosure in a particular order, this does not require or imply that these steps must be performed in that particular order, or that all of the steps must be performed, to achieve the desired results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In addition, in an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
An electronic device 400 according to such an embodiment of the invention is described below with reference to fig. 4. The electronic device 400 shown in fig. 4 is only an example and should not bring any limitation to the function and the scope of use of the embodiments of the present invention.
As shown in fig. 4, electronic device 400 is embodied in the form of a general purpose computing device. The components of electronic device 400 may include, but are not limited to: the at least one processing unit 410, the at least one memory unit 420, a bus 430 connecting different system components (including the memory unit 420 and the processing unit 410), and a display unit 440.
Wherein the storage unit stores program code that is executable by the processing unit 410 to cause the processing unit 410 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification.
The storage unit 420 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)421 and/or a cache memory unit 422, and may further include a read only memory unit (ROM) 423.
The storage unit 420 may also include a program/utility 424 having a set (at least one) of program modules 425, such program modules 425 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above-mentioned "exemplary methods" section of the present description, when said program product is run on the terminal device.
Referring to fig. 5, a program product 500 for implementing the above method according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including AN object oriented programming language such as Java, C + +, or the like, as well as conventional procedural programming languages, such as the "C" language or similar programming languages.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (17)
1. A code test control method, the method comprising:
acquiring a target test requirement;
determining a first code branch to be tested according to the target test requirement;
determining a first application program package to be tested according to the first code branch to be tested;
and sending the first application program package to be tested to a test terminal.
2. The method of claim 1, wherein sending the first application package under test to a test terminal comprises:
and sending the first application program package to be tested to the test terminal, and automatically installing the first application program package on the test terminal.
3. The method of claim 2, wherein sending the first application package under test to the test terminal and automatically installing on the test terminal comprises:
and sending the first application package to be tested to the test terminal, triggering the test terminal to automatically install the first application package to be tested, and prompting the test terminal to test the first application package to be tested after the installation is finished.
4. The method according to any one of claims 1 to 3, wherein sending the first application package under test to a test terminal comprises:
and determining a test terminal according to the target test requirement, and sending the first application package to be tested to the test terminal.
5. The method of claim 4, wherein the target test requirement comprises a requirement identification, and the test terminal is a terminal inputting the requirement identification.
6. The method of claim 5, wherein the test terminal inputs the requirement identifier by typing or scanning.
7. The method of claim 1, further comprising:
receiving a test result fed back by the test terminal;
if the test result is that the test is not passed, determining a second code branch to be tested, wherein the second code branch to be tested is a code branch to be tested obtained by repairing the first code branch to be tested;
automatically generating a second application program package to be tested according to the second code branch to be tested;
and sending the second application program package to be tested to the test terminal.
8. The method of claim 7, further comprising:
and if the test result is that the test is passed, indicating the code warehouse to merge the first code branch to be tested into the main code.
9. The method of claim 7, wherein determining the second branch of code under test comprises:
judging whether the first code branch to be tested is updated;
and if so, determining the updated first code branch to be tested as a second code branch to be tested.
10. The method of claim 7, further comprising: the sending the second application package to be tested to the test terminal includes:
and sending the second application program package to be tested to the test terminal, and automatically installing the second application program package on the test terminal.
11. The method of claim 10, wherein sending the second application package under test to the test terminal and automatically installing on the test terminal comprises:
and sending the second application program package to be tested to the test terminal, triggering the test terminal to automatically install the second application program package to be tested, and prompting the test terminal to test the second application program package to be tested after the installation is finished.
12. The method of claim 1, wherein the target test requirements comprise a requirement identification;
the determining a first code branch to be tested according to the target test requirement includes:
and determining a first code branch to be tested according to the requirement identification.
13. The method of claim 12, wherein prior to said determining a first branch of code under test as a function of said test requirement, said method further comprises:
establishing a mapping relation between a code branch to be tested and a requirement identifier;
the determining as the first code branch to be tested according to the requirement identifier includes:
and determining the code branch to be tested corresponding to the requirement identification as a first code branch to be tested according to the mapping relation.
14. The method of claim 1, wherein the first to-be-tested application package is generated by automatically packaging according to the first to-be-tested code branch before the target test requirement is obtained.
15. The application package testing method of claim 1, wherein the first application package under test comprises: android application packages.
16. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements the code test control method according to any one of claims 1 to 15.
17. An electronic device, comprising:
a processor;
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the code test control method of any one of claims 1-15 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010279147.4A CN111427795A (en) | 2020-04-10 | 2020-04-10 | Code test control method and device, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010279147.4A CN111427795A (en) | 2020-04-10 | 2020-04-10 | Code test control method and device, storage medium and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111427795A true CN111427795A (en) | 2020-07-17 |
Family
ID=71553819
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010279147.4A Withdrawn CN111427795A (en) | 2020-04-10 | 2020-04-10 | Code test control method and device, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111427795A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116775491A (en) * | 2023-06-26 | 2023-09-19 | 乾升利信息技术(上海)有限公司 | Project testing method and device, electronic equipment and storage medium |
-
2020
- 2020-04-10 CN CN202010279147.4A patent/CN111427795A/en not_active Withdrawn
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116775491A (en) * | 2023-06-26 | 2023-09-19 | 乾升利信息技术(上海)有限公司 | Project testing method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109840206B (en) | Data testing method, device, terminal and storage medium | |
| CN108319460B (en) | Method and device for generating application program installation package, electronic equipment and storage medium | |
| WO2019029160A1 (en) | Application construction method and system, computer device, and storage medium | |
| CN109634837B (en) | Automatic test method, device, equipment and storage medium | |
| US8978015B2 (en) | Self validating applications | |
| CN105446712B (en) | Application program defect repairing method and device | |
| CN109977670B (en) | Android application security monitoring method based on plug-in loading and storage medium | |
| US7069474B2 (en) | System and method for assessing compatibility risk | |
| CN104407973A (en) | Automatic unit test realizing method and device | |
| CN110674047B (en) | Software testing method and device and electronic equipment | |
| CN107643893B (en) | Program detection method and device | |
| CN106021101B (en) | The method and device that mobile terminal is tested | |
| CN107329889B (en) | Method for automatically testing C compiler | |
| CN112052169A (en) | Test management method, system, device and computer readable storage medium | |
| CN106648762B (en) | Method and device for building development environment | |
| CN112241360A (en) | Test case generation method, device, equipment and storage medium | |
| CN111930398B (en) | Application program updating method, device, system, medium and equipment | |
| CN105404574B (en) | Smart card and mobile terminal consistency test method and device | |
| CN112988578A (en) | Automatic testing method and device | |
| CN111427795A (en) | Code test control method and device, storage medium and electronic equipment | |
| CN113742215A (en) | Method and system for automatically configuring and calling test tool to perform test analysis | |
| CN116627850B (en) | Function debugging method and device, storage medium and electronic equipment | |
| CN112052037A (en) | Application software development method, device, equipment and medium | |
| CN113986744A (en) | Method and device for testing warehouse and table components and storage medium | |
| CN110928798A (en) | Code testing method, device and equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20200717 |
|
| WW01 | Invention patent application withdrawn after publication |