CN108415828B - Program testing method and device, readable storage medium and computer equipment - Google Patents
Program testing method and device, readable storage medium and computer equipment Download PDFInfo
- Publication number
- CN108415828B CN108415828B CN201810064820.5A CN201810064820A CN108415828B CN 108415828 B CN108415828 B CN 108415828B CN 201810064820 A CN201810064820 A CN 201810064820A CN 108415828 B CN108415828 B CN 108415828B
- Authority
- CN
- China
- Prior art keywords
- program
- docker container
- docker
- subprograms
- container
- 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.)
- Active
Links
- 238000004891 communication Methods 0.000 claims abstract description 32
- 230000010354 integration Effects 0.000 claims abstract description 15
- 238000000034 method Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims 1
- 238000012360 testing method Methods 0.000 abstract description 35
- 238000012827 research and development Methods 0.000 description 6
- 230000001419 dependent effect Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000010586 diagram Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000011160 research Methods 0.000 description 1
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
-
- 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/3664—Environments for testing or debugging software
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)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
A program testing method, an apparatus-readable storage medium, and a computer device, the program being split into a plurality of sub-programs, the program testing method comprising: acquiring a plurality of subprograms sent by an integration server, and storing the plurality of subprograms in a directory where a docker tool configuration file is located; and respectively starting a plurality of docker containers corresponding to the subprograms, and establishing communication connection between the docker containers corresponding to the associated subprograms. The embodiment of the invention ensures the safety of the source code of the program by splitting the program to be tested into a plurality of subprograms for testing, and the testing server establishes communication connection between the docker containers corresponding to the associated subprograms when executing the program test so as to ensure the normal operation of the program test.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a program testing method, an apparatus readable storage medium, and a computer device.
Background
After a general research and development personnel completes a program, the general research and development personnel need to test so as to find errors as early as possible and ensure the quality of developed products.
In the prior art, a deployment program test environment is generally performed by Jenkins in combination with docker. Research personnel submit programs to an integrated server, such as a Jenkins server, and the programs are compiled and packaged by the Jenkins server and then sent to a test server. Developers can package developed programs and dependencies into a portable container using a Docker container. And executing the program to be tested sent by the testing Jenkins server by starting the docker container.
In the prior art, when a program is tested, the safety of a source code of the program is one of important factors considered by a research and development personnel. In the existing program test, a program is usually packaged and sent to a test server as a whole, and in the sending and testing processes of the program, a source code is easy to leak and the safety is not high.
Disclosure of Invention
In view of the above, it is desirable to provide a program testing method, an apparatus readable storage medium and a computer device for solving the problem of low program testing safety in the prior art.
The embodiment of the invention provides a program testing method, wherein the program is divided into a plurality of sub-programs, and the program testing method comprises the following steps:
acquiring a plurality of subprograms sent by an integration server, and storing the plurality of subprograms in a directory where a docker tool configuration file is located;
and respectively starting a plurality of docker containers corresponding to the subprograms, and establishing communication connection between the docker containers corresponding to the associated subprograms.
The program testing method further comprises the following steps:
when an updated subprogram sent by an integration server is obtained, replacing a corresponding atomic program with the updated subprogram;
deleting the docker container corresponding to the atomic program, and establishing a new docker container;
and starting the new docker container and the related docker container, and establishing communication connection between the new docker container and the related docker container, wherein the related docker container is the docker container corresponding to the subprogram associated with the updated subprogram.
The program testing method further includes, before the step of deleting the docker container corresponding to the atomic program:
judging whether a docker container corresponding to the atomic program runs or not;
and if not, determining to delete the docker container corresponding to the atomic program.
The program testing method includes the steps of starting the new docker container and the related docker container:
acquiring an access address of the new docker container by using the related docker container;
according to the access address, circularly accessing the new docker container by using the related docker container to inquire whether the new docker container is started or not;
and when the related docker container judges that the new docker container is started, starting the related docker container.
The program testing method includes the following steps of storing the plurality of subprograms in a directory where the docker tool configuration file is located:
and hanging a plurality of subprograms in the docker tool configuration file in a disk mounting mode.
The present invention also provides a program testing apparatus, comprising:
the acquisition and storage unit is used for acquiring the plurality of subprograms sent by the integration server and storing the plurality of subprograms into a directory where the docker tool configuration file is located;
and the first communication establishing unit is used for respectively starting the docker containers corresponding to the plurality of subprograms and establishing communication connection between the docker containers corresponding to the related subprograms.
The program testing device further includes:
the replacing unit is used for replacing the corresponding atomic program with the updated subprogram when the updated subprogram sent by the integration server is obtained;
the container deleting and establishing unit is used for deleting the docker container corresponding to the atomic program and establishing a new docker container;
and the second communication establishing unit is used for starting the new docker container and the related docker container and establishing communication connection between the new docker container and the related docker container, wherein the related docker container is the docker container corresponding to the subprogram associated with the updated subprogram.
The program testing device further includes:
the judging unit is used for judging whether the docker container corresponding to the atomic program runs or not;
and the determining unit is used for determining to delete the docker container corresponding to the atomic program when the docker container corresponding to the atomic program does not operate.
The second communication establishing unit is further configured to:
acquiring an access address of the new docker container by using the related docker container;
according to the access address, circularly accessing the new docker container by using the related docker container to inquire whether the new docker container is started or not;
and when the related docker container judges that the new docker container is started, starting the related docker container.
Further, the acquisition and storage unit is further configured to:
and hanging a plurality of subprograms in the docker tool configuration file in a disk mounting mode.
An embodiment of the present invention further provides a readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the above method.
The invention also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the above method when executing the program.
The embodiment of the invention ensures the safety of the source code of the program by splitting the program to be tested into a plurality of subprograms for testing. When the test server executes the program test, firstly, the communication connection between the docker containers corresponding to the associated subprogram is established, so that data sharing is realized, the normal progress of the program test is ensured, and the reliability of the test result is ensured.
Drawings
FIG. 1 is a flowchart of a program testing method according to a first embodiment of the present invention;
FIG. 2 is a flowchart of a program test according to a first embodiment of the present invention;
FIG. 3 is a flowchart of a program testing method according to a second embodiment of the present invention;
FIG. 4 is a block diagram of a program testing apparatus according to a third embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the accompanying drawings are illustrative only for the purpose of explaining the present invention, and are not to be construed as limiting the present invention.
These and other aspects of embodiments of the invention will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the invention have been disclosed in detail as being indicative of some of the ways in which the principles of the embodiments of the invention may be practiced, but it is understood that the scope of the embodiments of the invention is not limited correspondingly. On the contrary, the embodiments of the invention include all changes, modifications and equivalents coming within the spirit and terms of the claims appended hereto.
Referring to fig. 1, a program testing method according to a first embodiment of the present invention is applied to a testing server, which is a computer device generally used by a tester and is also a host of a Docker container. In the embodiment, a project test environment is deployed through an integrated server, such as a Jenkins server and a docker. When a newly developed program of a research and development staff needs to be continuously integrated, a corresponding Docker container is constructed in a test server, and the program is tested by starting the corresponding Docker container. In this embodiment, in order to enhance the security of the source code of the program, the program to be tested is split into a plurality of subroutines, and each subroutine has its corresponding source code. The program testing method includes steps S11-S12.
And step S11, acquiring a plurality of subprograms sent by the integration server, and storing the plurality of subprograms in a directory where the docker tool configuration file is located.
A research and development staff divides a program to be tested into a plurality of sub programs, and then a docker container is respectively established for each sub program in a test server. Wherein the docker tool is docker composition, and the configuration file is docker-composition. Each service can be defined in the docker-composition.yaml, the dependency relationship between the mirror depended by each service and the container generated after each mirror runs is established, and the docker composition completes management and configuration of the docker container corresponding to each subprogram through the docker-composition.yaml file.
As shown in fig. 2, the developer submits each subprogram to the code library, the integration server obtains each subprogram from the code library, constructs and deploys the subprogram, and packages and sends each subprogram to the test server. And when receiving the code packet of each subprogram, the test server decompresses the code packet, and stores the decompressed subprogram into a directory in which a docker-compound.
The program to be tested is generally written in a compiled voice, such as C + + language or C language. In specific implementation, when the integrated server receives the subprogram, the integrated server compiles the source code of the subprogram to obtain a compiled binary program, the compiled binary program is not easy to crack, and the compiled binary program can be directly packed and sent to a tester, so that the safety of the code can be ensured, and the program testing efficiency can also be improved.
Step S12, respectively starting multiple docker containers corresponding to the subroutines, and establishing communication connection between the docker containers corresponding to the associated subroutines.
When a program is divided into a plurality of sub-programs, the operation of each sub-program has a dependency relationship with each other, that is, the operation of a certain sub-program depends on the data of one or more other sub-programs. The developer firstly determines the dependency relationship among the sub-programs, and determines the docker containers which are associated with each other according to the dependency relationship of the sub-programs. Therefore, when the test server receives each subprogram, the test server starts a plurality of docker containers corresponding to the subprograms and establishes communication connection between the docker containers corresponding to the associated subprograms, so that information interaction can be performed between the associated docker containers.
During program testing, a docker container is started through a docker-compound.yaml file, a program is executed, and a user detects whether the program is correct or not according to the program execution condition.
In the embodiment, the program to be tested is split into the plurality of sub programs for testing, so that the safety of the source code of the program is ensured. When the test server executes the program test, firstly, the communication connection between the docker containers corresponding to the associated subprogram is established, so that data sharing is realized, the normal progress of the program test is ensured, and the reliability of the test result is ensured.
After the program is tested, research and development personnel modify and perfect the source code of the program according to the test result. Testing of the program generally needs to be continued. Referring to fig. 3, a program testing method according to a second embodiment of the present invention is optimized based on the first embodiment, and when any one of the subroutines is updated, the program testing method further includes steps S21-S23.
Step S21, when an updated subprogram sent by the integration server is acquired, replacing the corresponding atomic program with the updated subprogram.
When the source code of one or more subroutines of a program is updated, a developer submits the updated subroutines into a code library. And the integration server acquires the updated subprogram for compiling, and packs and sends the compiled program to the test server. The test service deletes the old subprogram in the directory where the docker-composition.yaml file is located when receiving the updated subprogram, and decompresses the updated subprogram.
And step S22, deleting the docker container corresponding to the atomic program, and establishing a new docker container. And the new docker container is the docker container corresponding to the updated subprogram.
And when the test server receives an updated subprogram, judging whether a docker container corresponding to the atomic program is in operation or not. When a docker container corresponding to an atomic program is running, if only data of the container is updated, the program cannot be updated in place in the test process, and accuracy of a program test result is affected. Therefore, when the test server detects that the corresponding docker container is running, the docker container corresponding to the atomic program is stopped and deleted, that is, the original docker container is deleted. And then, establishing a new docker container corresponding to the updated subprogram code for testing the updated subprogram.
Step S23, starting the new docker container and the related docker container, and establishing communication connection between the new docker container and the related docker container. And the related docker container is a docker container corresponding to the subprogram associated with the updated subprogram.
When the original docker container is deleted, the communication connection between the original docker container and its associated docker container does not exist. And no communication connection is established between the established new docker container and the relevant docker container, so that information interaction cannot be carried out. Therefore, a communication connection between a new docker container and the associated docker container needs to be re-established.
Further, before step 22, it may also be determined whether the docker container corresponding to the atomic program is running, and when the docker container corresponding to the atomic program is running, step S22 is executed. When the docker container corresponding to the atomic program is not operated, that is, it is described that the docker container corresponding to the atomic program is not started or fails to be started, the reason for the situation may be that the program is wrong, and a developer updates the program. Therefore, when the test server receives the updated subprogram, the test server only needs to correspondingly update the data in the original docker container and restart the original docker container so as to establish the communication connection between the original docker container and the related docker container. Therefore, the original container does not need to be deleted, and the testing efficiency is improved.
Starting the new docker container and the related docker container can be realized by mounting a pre-written script program in the related docker container, initializing the related docker container to execute the script, and starting the related docker container after waiting for the normal start of the new docker container. The specific implementation process is as follows:
acquiring an access address of a new docker container by using a related docker container;
according to the access address, circularly accessing the new docker container by using the related docker container to inquire whether the new docker container is started;
and when the relevant docker container judges that a new docker container is started, starting the relevant docker container.
And circularly accessing the new docker container by the related docker container to inquire whether the new docker container is started or not, and starting the related docker container when the new docker container is inquired to be started.
For a plurality of docker containers with dependency relationships, due to the fact that one docker container is updated, a phenomenon that communication of the docker container which is dependent on the docker container is interrupted can occur. Therefore, the new first docker container and the second docker container are always in a communication connection state through a circular access mechanism. It will be appreciated that this mechanism can be employed by all associated docker containers to establish a communication connection.
When a traditional mode is used for deploying a test environment, a program to be tested and a mirror image are uniformly packaged, if different programs are encountered, but the dependent running environments are the same, the basic mirror image corresponding to the dependent environment is repeatedly copied, and the waste of the space of a test server is caused. Based on this problem, in the present embodiment, the subroutine is mounted in a docker-composition.yaml file in a disk mount manner. Preferably, each subroutine is mounted to a container to run in a docker-composition.yaml file by using volumes. Therefore, when the program is tested, the basic mirror image does not need to be updated every time the subprogram is updated, the program testing efficiency is improved, and the subprograms in the same running environment can share one basic mirror image, so that the waste of the storage space of the test server is avoided.
Referring to fig. 4, a program testing apparatus according to a third embodiment of the present invention includes:
the acquisition and storage unit 100 is configured to acquire a plurality of subprograms sent by the integration server, and store the plurality of subprograms in a directory where the docker tool configuration file is located;
the first communication establishing unit 200 is configured to respectively start multiple docker containers corresponding to the subroutines, and establish communication connection between the docker containers corresponding to the associated subroutines.
Further, the program testing apparatus further includes:
a replacing unit 300, configured to, when an updated subprogram sent by the integration server is obtained, replace the corresponding atomic program with the updated subprogram;
a container deleting and establishing unit 400, configured to delete the docker container corresponding to the atomic program, and establish a new docker container;
a second communication establishing unit 500, configured to start the new docker container and a related docker container, and establish a communication connection between the new docker container and the related docker container, where the related docker container is a docker container corresponding to a subroutine associated with the updated subroutine.
Further, the program testing apparatus further includes:
a determining unit 600, configured to determine whether a docker container corresponding to the atomic program runs;
a determining unit 700, configured to determine to delete the docker container corresponding to the atomic program when the docker container corresponding to the atomic program does not run.
The further second communication establishing unit 500 is further configured to:
acquiring an access address of the new docker container by using the related docker container;
according to the access address, circularly accessing the new docker container by using the related docker container to inquire whether the new docker container is started or not;
and when the related docker container judges that the new docker container is started, starting the related docker container.
Further, the obtaining and storing unit 100 is further configured to:
and hanging a plurality of subprograms in the docker tool configuration file in a disk mounting mode.
The apparatus of this embodiment may be used to implement the technical solution of any one of the method embodiments shown in fig. 1 and fig. 3, and the implementation principle and the technical effect are similar, which are not described herein again.
The present invention also provides a readable storage medium on which a computer program is stored, characterized in that the program, when executed by a processor, implements the steps of the method of any one of the above embodiments 1 to 2.
The invention also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any of the above embodiments 1 to 2 when executing the program.
The logic and/or steps represented in the flowcharts or otherwise described herein, e.g., an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following techniques, which are known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. A program testing method, wherein the program is divided into a plurality of sub-programs, the program testing method comprising:
acquiring a plurality of subprograms sent by an integration server, and storing the plurality of subprograms in a directory where a docker tool configuration file is located;
respectively starting a plurality of docker containers corresponding to the subprograms, and establishing communication connection between the docker containers corresponding to the associated subprograms;
during program testing, starting each docker container through a docker-compound.yaml file to execute the program and feed back a program testing result;
when an updated subprogram sent by an integration server is obtained, replacing a corresponding atomic program with the updated subprogram;
deleting the docker container corresponding to the atomic program, and establishing a new docker container;
and starting the new docker container and the related docker container, and establishing communication connection between the new docker container and the related docker container, wherein the related docker container is the docker container corresponding to the subprogram associated with the updated subprogram.
2. The program testing method of claim 1, wherein the step of deleting the docker container corresponding to the atomic program further comprises, before the step of deleting the docker container corresponding to the atomic program:
judging whether a docker container corresponding to the atomic program runs or not;
and if not, determining to delete the docker container corresponding to the atomic program.
3. The program test method of claim 1, wherein the step of initiating the new docker container and the associated docker container comprises:
acquiring an access address of the new docker container by using the related docker container;
according to the access address, circularly accessing the new docker container by using the related docker container to inquire whether the new docker container is started or not;
and when the related docker container judges that the new docker container is started, starting the related docker container.
4. The program testing method of claim 1, wherein the step of saving the plurality of subroutines to a directory in which a docker tool configuration file is located comprises:
and hanging a plurality of subprograms in the docker tool configuration file in a disk mounting mode.
5. A program test apparatus, comprising:
the acquisition and storage unit is used for acquiring a plurality of subprograms sent by the integration server and storing the plurality of subprograms into a directory where the docker tool configuration file is located;
the first communication establishing unit is used for respectively starting the docker containers corresponding to the plurality of subprograms and establishing communication connection between the docker containers corresponding to the related subprograms;
during program testing, starting each docker container through a docker-compound.yaml file to execute the program and feed back a program testing result;
the replacing unit is used for replacing the corresponding atomic program with the updated subprogram when the updated subprogram sent by the integration server is obtained;
the container deleting and establishing unit is used for deleting the docker container corresponding to the atomic program and establishing a new docker container;
and the second communication establishing unit is used for starting the new docker container and the related docker container and establishing communication connection between the new docker container and the related docker container, wherein the related docker container is the docker container corresponding to the subprogram associated with the updated subprogram.
6. The program test device of claim 5, further comprising:
the judging unit is used for judging whether the docker container corresponding to the atomic program runs or not;
and the determining unit is used for determining to delete the docker container corresponding to the atomic program when the docker container corresponding to the atomic program does not operate.
7. A readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method according to any one of claims 1-4.
8. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method according to any of claims 1-4 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810064820.5A CN108415828B (en) | 2018-01-23 | 2018-01-23 | Program testing method and device, readable storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810064820.5A CN108415828B (en) | 2018-01-23 | 2018-01-23 | Program testing method and device, readable storage medium and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108415828A CN108415828A (en) | 2018-08-17 |
| CN108415828B true CN108415828B (en) | 2021-09-24 |
Family
ID=63126295
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810064820.5A Active CN108415828B (en) | 2018-01-23 | 2018-01-23 | Program testing method and device, readable storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108415828B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109359033A (en) * | 2018-09-05 | 2019-02-19 | 广州神马移动信息科技有限公司 | Method for testing pressure, testing service device, management server and system |
| CN109324819A (en) * | 2018-09-28 | 2019-02-12 | 中国平安财产保险股份有限公司 | Code server dispositions method, device, server apparatus and storage medium |
| CN111258915B (en) * | 2020-02-27 | 2023-07-04 | 成都乐创自动化技术股份有限公司 | Method for carrying out automatic unit test on PLC program |
| CN111831396A (en) * | 2020-07-10 | 2020-10-27 | 融慧金科金融服务外包（北京）有限公司 | Docker software and hardware integration-based delivery method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8607328B1 (en) * | 2005-03-04 | 2013-12-10 | David Hodges | Methods and systems for automated system support |
| CN105701010A (en) * | 2015-12-31 | 2016-06-22 | 北京元心科技有限公司 | Method and device for accelerating software testing |
| CN107003862A (en) * | 2014-09-30 | 2017-08-01 | 亚马逊技术有限公司 | Dynamic code is disposed and versioned |
| CN107493191A (en) * | 2017-08-08 | 2017-12-19 | 深信服科技股份有限公司 | A kind of clustered node and self scheduling container group system |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101833455B (en) * | 2010-05-13 | 2012-10-10 | 北京大学 | Code splitting method for converting traditional software into rich client software |
| US9262250B2 (en) * | 2011-12-12 | 2016-02-16 | Crashlytics, Inc. | System and method for data collection and analysis of information relating to mobile applications |
| US10162735B2 (en) * | 2015-09-30 | 2018-12-25 | Red Hat, Inc. | Distributed system test automation framework |
| CN105224466B (en) * | 2015-11-17 | 2018-08-28 | 广州亦云信息技术有限公司 | A kind of integration test method and system based on Docker |
| CN105550130A (en) * | 2015-12-14 | 2016-05-04 | 中电科华云信息技术有限公司 | Container based dynamic arrangement method for application environment and system applying method |
| CN105653449A (en) * | 2015-12-28 | 2016-06-08 | 湖南蚁坊软件有限公司 | Continuous integration method based on container virtualization |
| US11822970B2 (en) * | 2016-06-24 | 2023-11-21 | Nicira, Inc. | Identifier (ID) allocation in a virtualized computing environment |
| EP3267351A1 (en) * | 2016-07-07 | 2018-01-10 | Gemalto Sa | Method for securely managing a docker image |
| CN106550033A (en) * | 2016-10-27 | 2017-03-29 | 普元信息技术股份有限公司 | Based on the system and method that cloud computing system realizes simulation the whole network ability open platform |
| CN107294772B (en) * | 2017-05-23 | 2020-09-01 | 中电万维信息技术有限责任公司 | Dynamic management monitoring service system combined with Docker |
-
2018
- 2018-01-23 CN CN201810064820.5A patent/CN108415828B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8607328B1 (en) * | 2005-03-04 | 2013-12-10 | David Hodges | Methods and systems for automated system support |
| CN107003862A (en) * | 2014-09-30 | 2017-08-01 | 亚马逊技术有限公司 | Dynamic code is disposed and versioned |
| CN105701010A (en) * | 2015-12-31 | 2016-06-22 | 北京元心科技有限公司 | Method and device for accelerating software testing |
| CN107493191A (en) * | 2017-08-08 | 2017-12-19 | 深信服科技股份有限公司 | A kind of clustered node and self scheduling container group system |
Non-Patent Citations (1)
| Title |
|---|
| 基于SOA的高并发与高可用网站开发框架设计与实现;田浩;《中国优秀硕士学位论文全文数据库 信息科技辑》;20171215;I139-234 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108415828A (en) | 2018-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108415828B (en) | Program testing method and device, readable storage medium and computer equipment | |
| US6385766B1 (en) | Method and apparatus for windows-based installation for installing software on build-to-order computer systems | |
| US10114637B1 (en) | Automatically updating a shared project build platform | |
| US10579966B1 (en) | Adapting a shared project build platform to a developer plugin | |
| US20190235993A1 (en) | Generating an inner cloud environment within an outer cloud environment for testing a microservice application | |
| CN108399132B (en) | Scheduling test method, device and storage medium | |
| US9582268B2 (en) | Automatic communications graphing for a source application | |
| US8296758B2 (en) | Deployment and versioning of applications | |
| US20160306737A1 (en) | Automated error checking system for a software application and method therefor | |
| US8745610B2 (en) | Maintenance system, maintenance method and program for maintenance | |
| CN113703730A (en) | Continuous integration method and device, computer equipment and storage medium | |
| US20040054988A1 (en) | Certification test suite | |
| CN112835676A (en) | Deployment method and device of containerized application, computer equipment and medium | |
| US9542173B2 (en) | Dependency handling for software extensions | |
| JP2004158012A (en) | System and method for software application management | |
| CN110597544A (en) | Software system upgrading method and device | |
| CN113642004A (en) | Container mirror image security scanning and repairing method, device and equipment | |
| CN114546819A (en) | Code processing method and device, electronic equipment and readable medium | |
| CN115185644A (en) | Detection method, system, equipment and storage medium based on container interactive application | |
| CN109471799B (en) | Method, device, storage medium and terminal for deploying demand environment | |
| US9760364B2 (en) | Checks for software extensions | |
| CN106802846A (en) | A kind of remote test method, apparatus and system | |
| CN112286543B (en) | Application service deployment method and device | |
| CN116775061A (en) | Deployment method, device, equipment and storage medium of micro-service application | |
| CN110196730B (en) | Hot patch management method, device and storage medium of application program |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |