CN112328473A - Code automation integration test method and device and electronic equipment - Google Patents
Code automation integration test method and device and electronic equipment Download PDFInfo
- Publication number
- CN112328473A CN112328473A CN202011171113.XA CN202011171113A CN112328473A CN 112328473 A CN112328473 A CN 112328473A CN 202011171113 A CN202011171113 A CN 202011171113A CN 112328473 A CN112328473 A CN 112328473A
- Authority
- CN
- China
- Prior art keywords
- code
- result
- test
- generate
- integration
- 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
Abstract
The disclosure relates to a code automation integration test method, a code automation integration test device, an electronic device and a computer readable medium. The method comprises the following steps: acquiring a code to be tested; constructing the code by a Jenkins technology to generate a constructed code; performing integration test on the constructed code in a first test mode to generate a first result; performing an integration test on the constructed code in a second test mode to generate a second result; and generating an automated integration test report according to the first result and the second result. The code automation integration test method, the code automation integration test device, the electronic equipment and the computer readable medium can seamlessly connect development and test flows to form a closed loop from development to test to development, can also realize continuous integration of application development, and improve the application development efficiency.
Description
Technical Field
The disclosure relates to the field of computer information processing, in particular to a code automation integration test method and device, electronic equipment and a computer readable medium.
Background
Integration testing (also called assembly testing, joint testing) is a logical extension of unit testing. It is in its simplest form: two tested units are combined into one component, and the interface between the two components is tested. In this layer sense, a component refers to an integrated aggregation of multiple units. In a real-world scenario, many units are combined into components, which are in turn aggregated into a larger portion of the program. The method is to test the combination of fragments and finally expand into a process, testing the module together with other groups of modules. Finally, all modules that make up the process are tested together. Furthermore, if a program consists of multiple processes, they should be tested in pairs, rather than testing all processes simultaneously.
Problems arise when testing the combined unit for integration. By using a test plan that requires testing each unit before combining the units and ensuring the viability of each unit, it can be known that any errors discovered when combining the units are likely to be related to the interface between the units. This approach reduces the number of possible occurrences to a simpler level of analysis. An efficient integration test helps to solve the problems of compatibility and operability of the associated software with other systems. At present, in the integrated test, the development process and the test process of the software are transferred by manually submitting codes, so that the efficiency is low.
Therefore, a new code automated integration testing method, apparatus, electronic device and computer readable medium are needed.
The above information disclosed in this background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not constitute prior art that is already known to a person of ordinary skill in the art.
Disclosure of Invention
In view of this, the present disclosure provides a code automation integration test method, device, electronic device and computer readable medium, which can seamlessly join a development and test flow to form a closed loop from development to test to development, and can also implement continuous integration of application development, thereby improving application development efficiency.
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, a method for testing code automation integration is provided, the method including: acquiring a code to be tested; constructing the code by a Jenkins technology to generate a constructed code; performing integration test on the constructed code in a first test mode to generate a first result; performing an integration test on the constructed code in a second test mode to generate a second result; and generating an automated integration test report according to the first result and the second result.
Optionally, the method further comprises: when the first result and the second result both pass the integration test, packaging the codes and enabling the codes to be online; and when any result of the first result and the second result fails the integration test, generating an error tracing report.
Optionally, obtaining a code to be tested includes: and acquiring the code to be tested from the construction pool.
Optionally, the constructing the code by Jenkins technology to generate a constructed code, including: determining code information of the code; determining a storage location of the code in the build pool; determining a construction trigger and constructing an execution environment; and generating a construction code based on the information.
Optionally, determining a build trigger and building an execution environment includes: and determining a parameter as a built trigger of Poll SCM to periodically detect the change of the code.
Optionally, after generating the build code based on the information, the method further includes: and determining the release format of the test result.
Optionally, performing an integration test on the build code in a first test mode to generate a first result, where the generating includes: after the code is successfully constructed, generating a test task based on the relevant information of the code; sending the test task to at least one target server; the at least one target server carries out integration test on the construction code through an automatic test method to generate a first result.
Optionally, performing an integration test on the build code in a second test mode to generate a second result, including: after the code is successfully constructed, generating test reminding information based on the relevant information of the code; sending the test reminding information to at least one target client; the at least one target client performs an integration test on the build code to generate a second result.
Optionally, when any one of the first result and the second result fails the integration test, generating an error tracing report, including: and when the first result fails the integration test, automatically extracting error information based on the construction code, and generating an error tracing report, wherein the error tracing report comprises error positioning.
Optionally, when any one of the first result and the second result fails the integration test, generating an error tracing report, including: when the second result fails the integration test, generating a verification template based on the second result; sending the verification template to a client to acquire verification information; and generating an error tracing report based on the checking information, wherein the error tracing report comprises error positioning.
According to an aspect of the present disclosure, a code automation integration test apparatus is provided, the apparatus including: the code module is used for acquiring a code to be tested; the building module is used for building the codes through Jenkins technology to generate building codes; the first testing module is used for carrying out integration testing on the construction code through a first testing mode to generate a first result; the second testing module is used for carrying out integration testing on the construction code through a second testing mode to generate a second result; and the report module is used for generating an automatic integrated test report according to the first result and the second result.
Optionally, the method further comprises: the online module is used for packaging the codes and online when the first result and the second result both pass the integration test; and the source tracing module is used for generating an error source tracing report when any result of the first result and the second result fails the integration test.
Optionally, the code module is further configured to obtain the code to be tested from a building pool.
Optionally, the building module includes: an information unit for determining code information of the code; a location unit for determining a storage location of the code in the build pool; the parameter unit is used for determining a construction trigger and constructing an execution environment; and the construction unit is used for generating construction codes based on the information.
Optionally, the parameter unit is further configured to determine that the parameter is a configuration trigger of a Poll SCM, so as to periodically detect a change of the code.
Optionally, the building module further includes: and the format unit is used for determining the release format of the test result.
Optionally, the first test module includes: the task unit is used for generating a test task based on the relevant information of the code after the construction is successful; the first sending unit is used for sending the test task to at least one target server; the first testing unit is used for the at least one target server to carry out integration testing on the constructed code through an automatic testing method so as to generate a first result.
Optionally, the second test module includes: the reminding unit is used for generating test reminding information based on the relevant information of the code after the construction is successful; the second sending unit is used for sending the test reminding information to at least one target client; and the second testing unit is used for performing integrated testing on the building code by the at least one target client to generate a second result.
Optionally, the source tracing module is further configured to, when the first result fails the integration test, automatically extract error information based on the build code, and generate an error report, where the error report includes error location.
Optionally, the tracing module is further configured to generate a verification template based on the second result when the second result fails the integration test; sending the verification template to a client to acquire verification information; and generating an error report based on the checking information, wherein the error report comprises error positioning.
According to an aspect of the present disclosure, an electronic device is provided, the electronic device including: one or more processors; storage means for storing one or more programs; when executed by one or more processors, cause the one or more processors to implement a method as above.
According to an aspect of the disclosure, a computer-readable medium is proposed, on which a computer program is stored, which program, when being executed by a processor, carries out the method as above.
According to the code automatic integration test method, the device, the electronic equipment and the computer readable medium, a code to be tested is obtained; constructing the code by a Jenkins technology to generate a constructed code; performing integration test on the constructed code in a first test mode to generate a first result; performing an integration test on the constructed code in a second test mode to generate a second result; according to the mode of generating the automatic integrated test report according to the first result and the second result, the development and test processes can be seamlessly connected, a closed loop from development to test to development is formed, continuous integration of application development can be realized, and the application development 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 above and other objects, features and advantages of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings. The drawings described below are merely some embodiments of the present disclosure, and other drawings may be derived from those drawings by those of ordinary skill in the art without inventive effort.
Fig. 1 is a system block diagram illustrating a code automation integration testing method and apparatus according to an example embodiment.
FIG. 2 is a flow diagram illustrating a method for automated integration testing of code in accordance with an exemplary embodiment.
FIG. 3 is a flow chart illustrating a method for automated code integration testing according to another exemplary embodiment.
FIG. 4 is a flowchart illustrating a method of code automation integration testing according to another example embodiment.
FIG. 5 is a block diagram illustrating a code automation integration test device in accordance with an exemplary embodiment.
FIG. 6 is a block diagram illustrating an electronic device in accordance with an example embodiment.
FIG. 7 is a block diagram illustrating a computer-readable medium in accordance with an example embodiment.
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 embodiments 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 same reference numerals denote the same or similar parts in the drawings, and thus, a repetitive description thereof will be omitted.
Furthermore, 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 so forth. In other instances, well-known methods, devices, implementations, or operations have not been shown or described in detail to avoid obscuring aspects of the disclosure.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
It will be understood that, although the terms first, second, third, etc. may be used herein to describe various components, these components should not be limited by these terms. These terms are used to distinguish one element from another. Thus, a first component discussed below may be termed a second component without departing from the teachings of the disclosed concept. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
It is to be understood by those skilled in the art that the drawings are merely schematic representations of exemplary embodiments, and that the blocks or processes shown in the drawings are not necessarily required to practice the present disclosure and are, therefore, not intended to limit the scope of the present disclosure.
Fig. 1 is a system block diagram illustrating a code automation integration testing method and apparatus according to an example embodiment.
As shown in fig. 1, the system architecture 10 may include terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the terminal devices 101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.
The user may use the terminal devices 101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The terminal devices 101, 102, 103 may have various communication client applications installed thereon, such as a financial services application, a shopping application, a web browser application, an instant messaging tool, a mailbox client, social platform software, and the like.
The terminal devices 101, 102, 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 105 may be a server that provides various software testing services, such as a background management server that performs integrated testing of code developed by users using the terminal devices 101, 102, 103. The server 105 may analyze and the like the received code and feed back the processing result to the administrator of the website and/or the terminal apparatuses 101, 102, 103.
The server 105 may, for example, obtain the code to be tested; the server 105 may, for example, build the code via Jenkins technology, generating a build code; the server 105 may perform an integration test on the build code, for example, by using a first test mode, to generate a first result; the server 105 may perform an integration test on the build code, for example, by using a second test mode, to generate a second result; the server 105 may generate an automated integrated test report, for example, based on the first result and the second result.
The server 105 may be a physical server, or may be composed of a plurality of servers, for example, it should be noted that the code automation integration test method provided by the embodiment of the present disclosure may be executed by the server 105, and accordingly, the code automation integration test apparatus may be disposed in the server 105. And the development end provided for the user to develop the code is generally located in the terminal devices 101, 102, 103.
FIG. 2 is a flow diagram illustrating a method for automated integration testing of code in accordance with an exemplary embodiment. The code automation integration test method 20 includes at least steps S202 to S210.
As shown in fig. 2, in S202, a code to be tested is acquired. The code to be tested may be obtained from a build pool.
More specifically, the developer can normally perform the required development, and submit the code after the development is completed. The server can determine the updating of the code through the timing scanning task, and when the code is updated, the code mode is used for building a pool.
In S204, the code is constructed through Jenkins technology to generate a constructed code. The method comprises the following steps: determining code information of the code; determining a storage location of the code in the build pool; determining a construction trigger and constructing an execution environment; and generating a construction code based on the information.
More specifically, code information such as names, descriptions, etc. may be added to the code, and then the relevant location information may be entered for invocation at test time based on the actual location at which the code is stored.
In one embodiment, determining a build trigger, building an execution environment, comprises: and determining a parameter as a built trigger of Poll SCM to periodically detect the change of the code. The trigger can be a trigger for constructing a test task and can be triggered and constructed on a code level through a preset interface; and a Poll SCM command can be added, and when the code warehouse is changed, the code warehouse can be periodically checked whether to be changed or not based on the function provided by the Poll SCM command.
In one embodiment, after generating the build code based on the above information, the method further includes: and determining the release format of the test result.
In S206, an integration test is performed on the build code in a first test mode to generate a first result. The method comprises the following steps: after the code is successfully constructed, generating a test task based on the relevant information of the code; sending the test task to at least one target server; the at least one target server carries out integration test on the construction code through an automatic test method to generate a first result. The code may be integrity tested by a local server to generate a first result.
In S208, an integration test is performed on the build code in a second test mode to generate a second result. The method comprises the following steps: after the code is successfully constructed, generating test reminding information based on the relevant information of the code; sending the test reminding information to at least one target client; the at least one target client performs an integration test on the build code to generate a second result.
The code may also be tested by the remote client, where it may be tested in a user-assisted manner.
In S210, an automated integration test report is generated according to the first result and the second result. The first result is a result generated by the automated integration test, the second result is a test result generated by manual assistance, and the first result and the second result can reflect information such as errors or bugs in the codes from different angles. The first result and the second result are combined to generate a test report, so that the test problem can be more accurately determined.
According to the code automation integration test method, a code to be tested is obtained; constructing the code by a Jenkins technology to generate a constructed code; performing integration test on the constructed code in a first test mode to generate a first result; performing an integration test on the constructed code in a second test mode to generate a second result; according to the mode of generating the automatic integrated test report according to the first result and the second result, the development and test processes can be seamlessly connected, a closed loop from development to test to development is formed, continuous integration of application development can be realized, and the application development efficiency is improved.
It should be clearly understood that this disclosure describes how to make and use particular examples, but the principles of this disclosure are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.
FIG. 3 is a flow chart illustrating a method for automated code integration testing according to another exemplary embodiment. The process 30 shown in fig. 3 is a supplementary description of the process shown in fig. 2.
As shown in fig. 3, in S302, when both the first result and the second result pass the integration test, the code is packaged on line. And setting parameter information related to online for the code according to preset online time, and further packaging.
In S304, when any one of the first result and the second result fails the integration test, an error tracing report is generated.
In S306, when the first result fails the integration test, automatically extracting error information based on the build code, and generating an error report, where the error report includes error locations. Error information can be extracted, arranged according to the sending time and the operation sequence, and then the relevance of code errors is checked one by one from back to front in a recursive mode so as to attribute the codes with the relevance errors in an error category.
In S308, when the second result fails the integration test, generating a verification template based on the second result; sending the verification template to a client to acquire verification information; and generating an error report based on the checking information, wherein the error report comprises error positioning. And extracting a verification template set from the database, wherein the verification template set comprises a plurality of verification templates related to code errors, and extracting the related verification templates according to the error information in the second result. And sending the verification template to the client so that the client supplements the parameter information in the verification template according to the second result. And finally generating an error report according to the check template with the parameters.
FIG. 4 is a flowchart illustrating a method of code automation integration testing according to another example embodiment. The process 40 shown in fig. 4 is a further description of the process shown in fig. 2.
As shown in fig. 4, in S402, the developer submits code.
In S404, a code is detected.
In S406, Jenkins constructs a code.
At S408, the test code is automated.
In S410, the code is remotely tested.
In S412, the test passes.
In S414, an error report is transmitted. Jenkins sends error reports to related personnel; and the developer repairs the bug according to the error information and enters a new process.
In S416, the line is packaged.
According to the code automatic integration test method disclosed by the invention, the code is tested based on the Jenkins technology, the development and test processes are seamlessly connected, and continuous integration is realized.
Those skilled in the art will appreciate that all or part of the steps implementing the above embodiments are implemented as computer programs executed by a CPU. When executed by the CPU, performs the functions defined by the above-described methods provided by the present disclosure. The program may be stored in a computer readable storage medium, which may be a read-only memory, a magnetic or optical disk, or the like.
Furthermore, it should be noted that the above-mentioned figures are only schematic illustrations of the processes involved in the methods according to exemplary embodiments of the present disclosure, and are not intended to be limiting. It will be readily understood that the processes shown in the above figures are not intended to indicate or limit the chronological order of the processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, e.g., in multiple modules.
The following are embodiments of the disclosed apparatus that may be used to perform embodiments of the disclosed methods. For details not disclosed in the embodiments of the apparatus of the present disclosure, refer to the embodiments of the method of the present disclosure.
FIG. 5 is a block diagram illustrating a code automation integration test device in accordance with an exemplary embodiment. As shown in fig. 5, the code automation integration test apparatus 50 includes: the code module 502, the building module 504, the first testing module 506, the second testing module 508, the reporting module 510, and the code automation integration testing device 50 may further include: an online module 512 and a source tracing module 514.
The code module 502 is used for acquiring a code to be tested; the code module 502 is also configured to obtain the code to be tested from the building pool.
The building module 504 is configured to build the code by Jenkins technology to generate a building code; the building module 504 includes: an information unit for determining code information of the code; a location unit for determining a storage location of the code in the build pool; the parameter unit is used for determining a construction trigger and constructing an execution environment; the parameter unit is further configured to determine that a parameter is a configuration trigger of a Poll SCM, so as to periodically detect a change of the code. The format unit is used for determining the release format of the test result; and the construction unit is used for generating construction codes based on the information.
The first testing module 506 is configured to perform an integration test on the build code in a first testing manner to generate a first result; the first testing module 506 comprises: the task unit is used for generating a test task based on the relevant information of the code after the construction is successful; the first sending unit is used for sending the test task to at least one target server; the first testing unit is used for the at least one target server to carry out integration testing on the constructed code through an automatic testing method so as to generate a first result.
The second testing module 508 is configured to perform an integration test on the build code in a second testing manner to generate a second result; the second testing module 508 includes: the reminding unit is used for generating test reminding information based on the relevant information of the code after the construction is successful; the second sending unit is used for sending the test reminding information to at least one target client; and the second testing unit is used for performing integrated testing on the building code by the at least one target client to generate a second result.
The reporting module 510 is configured to generate an automated integration test report according to the first result and the second result. The reporting module 510 is further configured to, when the first result fails the integration test, automatically extract error information based on the build code, and generate an error report, where the error report includes error locations. The report module 510 is further configured to generate a verification template based on the second result when the second result fails the integration test; sending the verification template to a client to acquire verification information; and generating an error report based on the checking information, wherein the error report comprises error positioning.
The online module 512 is configured to package the code and online when both the first result and the second result pass the integration test;
the tracing module 514 is configured to generate an error tracing report when any one of the first result and the second result fails the integration test.
According to the code automation integration testing device disclosed by the invention, a code to be tested is obtained; constructing the code by a Jenkins technology to generate a constructed code; performing integration test on the constructed code in a first test mode to generate a first result; performing an integration test on the constructed code in a second test mode to generate a second result; according to the mode of generating the automatic integrated test report according to the first result and the second result, the development and test processes can be seamlessly connected, a closed loop from development to test to development is formed, continuous integration of application development can be realized, and the application development efficiency is improved.
FIG. 6 is a block diagram illustrating an electronic device in accordance with an example embodiment.
An electronic device 600 according to this embodiment of the disclosure is described below with reference to fig. 6. The electronic device 600 shown in fig. 6 is only an example and should not bring any limitations to the function and scope of use of the embodiments of the present disclosure.
As shown in fig. 6, the electronic device 600 is embodied in the form of a general purpose computing device. The components of the electronic device 600 may include, but are not limited to: at least one processing unit 610, at least one storage unit 620, a bus 630 that connects the various system components (including the storage unit 620 and the processing unit 610), a display unit 640, and the like.
Wherein the storage unit stores program code that is executable by the processing unit 610 such that the processing unit 610 performs steps in accordance with various exemplary embodiments of the present disclosure in the present specification. For example, the processing unit 610 may perform the steps as shown in fig. 2, 3, 4.
The storage unit 620 may include readable media in the form of volatile memory units, such as a random access memory unit (RAM)6201 and/or a cache memory unit 6202, and may further include a read-only memory unit (ROM) 6203.
The memory unit 620 may also include a program/utility 6204 having a set (at least one) of program modules 6205, such program modules 6205 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.
The electronic device 600 may also communicate with one or more external devices 600' (e.g., keyboard, pointing device, bluetooth device, etc.), such that a user can communicate with devices with which the electronic device 600 interacts, and/or any device (e.g., router, modem, etc.) with which the electronic device 600 can communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 600 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet) via the network adapter 660. The network adapter 660 may communicate with other modules of the electronic device 600 via the bus 630. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
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, as shown in fig. 7, the technical solution according to the embodiment 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, or a network device, etc.) to execute the above method according to the embodiment of the present disclosure.
The software 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.
The computer readable storage 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 storage 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 storage 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 for the present disclosure 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 and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).
The computer readable medium carries one or more programs which, when executed by a device, cause the computer readable medium to perform the functions of: acquiring a code to be tested; constructing the code by a Jenkins technology to generate a constructed code; performing integration test on the constructed code in a first test mode to generate a first result; performing an integration test on the constructed code in a second test mode to generate a second result; and generating an automated integration test report according to the first result and the second result.
Those skilled in the art will appreciate that the modules described above may be distributed in the apparatus according to the description of the embodiments, or may be modified accordingly in one or more apparatuses unique from the embodiments. The modules of the above embodiments may be combined into one module, or further split into multiple sub-modules.
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.
Exemplary embodiments of the present disclosure are specifically illustrated and described above. It is to be understood that the present disclosure is not limited to the precise arrangements, instrumentalities, or instrumentalities described herein; on the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (10)
1. A code automation integration test method is characterized by comprising the following steps:
acquiring a code to be tested;
constructing the code by a Jenkins technology to generate a constructed code;
performing integration test on the constructed code in a first test mode to generate a first result;
performing an integration test on the constructed code in a second test mode to generate a second result;
and generating an automated integration test report according to the first result and the second result.
2. The method of claim 1, further comprising:
when the first result and the second result both pass the integration test, packaging the codes and enabling the codes to be online;
and when any result of the first result and the second result fails the integration test, generating an error tracing report.
3. The method of any of claims 1-2, wherein obtaining code to be tested comprises:
and acquiring the code to be tested from the construction pool.
4. The method of any one of claims 1-3, wherein building the code by Jenkins technique to generate a build code comprises:
determining code information of the code;
determining a storage location of the code in the build pool;
determining a construction trigger and constructing an execution environment;
and generating a construction code based on the information.
5. The method of any of claims 1-4, wherein determining a build trigger, building an execution environment, comprises:
and determining a parameter as a built trigger of Pol l SCM to periodically detect the change of the code.
6. The method of any of claims 1-5, wherein after generating the build code based on the information, further comprising:
and determining the release format of the test result.
7. The method of any of claims 1-6, wherein performing an integration test on the build code via a first test mode to generate a first result comprises:
after the code is successfully constructed, generating a test task based on the relevant information of the code;
sending the test task to at least one target server;
the at least one target server carries out integration test on the construction code through an automatic test method to generate a first result.
8. An automated code integration test apparatus, comprising:
the code module is used for acquiring a code to be tested;
the building module is used for building the codes through Jenkins technology to generate building codes;
the first testing module is used for carrying out integration testing on the construction code through a first testing mode to generate a first result;
the second testing module is used for carrying out integration testing on the construction code through a second testing mode to generate a second result;
and the report module is used for generating an automatic integrated test report according to the first result and the second result.
9. An electronic device, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011171113.XA CN112328473A (en) | 2020-10-28 | 2020-10-28 | Code automation integration test method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011171113.XA CN112328473A (en) | 2020-10-28 | 2020-10-28 | Code automation integration test method and device and electronic equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112328473A true CN112328473A (en) | 2021-02-05 |
Family
ID=74296466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011171113.XA Withdrawn CN112328473A (en) | 2020-10-28 | 2020-10-28 | Code automation integration test method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112328473A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778507A (en) * | 2021-07-26 | 2021-12-10 | 北京芬香科技有限公司 | Supporting pipe type online method and system |
-
2020
- 2020-10-28 CN CN202011171113.XA patent/CN112328473A/en not_active Withdrawn
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113778507A (en) * | 2021-07-26 | 2021-12-10 | 北京芬香科技有限公司 | Supporting pipe type online method and system |
| CN113778507B (en) * | 2021-07-26 | 2024-02-20 | 北京芬香科技有限公司 | Method and system for supporting pipe type online |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20180011780A1 (en) | Web application test script generation to test software functionality | |
| US9218270B2 (en) | Functional software testing framework for determinate level testing | |
| US7784025B2 (en) | Mechanism for using processlets to model service processes | |
| CN111309343B (en) | Development deployment method and device | |
| US10037431B2 (en) | Software-as-a-service reference process extension verification framework | |
| CN112685029A (en) | Visual template generation method, device, equipment and storage medium | |
| CN112527382B (en) | Method for deploying pipeline engine system, and method and device for continuous integration | |
| US8180659B2 (en) | Identifying and measuring adherence to software development requirements | |
| CN113326247A (en) | Cloud data migration method and device and electronic equipment | |
| CN109840192B (en) | Method and device for automatic testing | |
| CN115576817A (en) | Automatic test system, method, electronic equipment and storage medium | |
| CN109460363B (en) | Automatic testing method and device, electronic equipment and computer readable medium | |
| CN112328473A (en) | Code automation integration test method and device and electronic equipment | |
| CN112988578A (en) | Automatic testing method and device | |
| US20210334096A1 (en) | Detecting bias in artificial intelligence software by analysis of source code contributions | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN115509602A (en) | Project management method, device, equipment and storage medium | |
| CN111865726B (en) | Service message testing method, device, computer system and storage medium | |
| CN113918525A (en) | Data exchange scheduling method, system, electronic device, medium, and program product | |
| CN114693116A (en) | Method and device for detecting code review validity and electronic equipment | |
| CN113344691A (en) | Tax declaration data processing method and device, electronic device and readable medium | |
| CN108170557B (en) | Method and apparatus for outputting information | |
| CN116560819B (en) | RPA-based batch automatic operation method, system, equipment and storage medium | |
| US11809308B2 (en) | System and framework for testing of application performance with real-time scaled simulation | |
| CN114201410A (en) | Method, device, equipment and medium for monitoring executed degree of test case |
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: 20210205 |
|
| WW01 | Invention patent application withdrawn after publication |