CN113050982A - Distributed code automatic publishing system and method - Google Patents
Distributed code automatic publishing system and method Download PDFInfo
- Publication number
- CN113050982A CN113050982A CN202110310634.7A CN202110310634A CN113050982A CN 113050982 A CN113050982 A CN 113050982A CN 202110310634 A CN202110310634 A CN 202110310634A CN 113050982 A CN113050982 A CN 113050982A
- Authority
- CN
- China
- Prior art keywords
- code
- issued
- test
- automatic
- release
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 27
- 238000012360 testing method Methods 0.000 claims abstract description 120
- 238000012544 monitoring process Methods 0.000 claims description 24
- 238000011056 performance test Methods 0.000 claims description 10
- 238000004806 packaging method and process Methods 0.000 claims description 5
- 230000010354 integration Effects 0.000 claims description 4
- 230000006835 compression Effects 0.000 description 4
- 238000007906 compression Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 238000011161 development Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000011990 functional testing Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3692—Test management for test results analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F21/577—Assessing vulnerabilities and evaluating computer system security
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/03—Indexing scheme relating to G06F21/50, monitoring users, programs or devices to maintain the integrity of platforms
- G06F2221/033—Test or assess software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Stored Programmes (AREA)
Abstract
The invention discloses a distributed code automatic release system and a distributed code automatic release method, which belong to the technical field of computers, and comprise the steps of receiving a code to be released, testing and generating corresponding version information, wherein the code to be released comprises a code text, acquiring the version information and the code text, uploading the version information and the code text to a git tool end for marking, obtaining a code text corresponding to the marked version information, grabbing the code text corresponding to the marked version information from the git tool end based on a jenkins release end, compiling, and generating a release code corresponding to the code to be released; and finally, the jenkins issuing end pushes the generated issuing code to an online server to realize automatic issuing. The method and the system have the advantages that the code to be issued is tested for multiple times, the tested code to be issued is compiled through the git tool end mark and the jenkins issuing end, the generated issuing code is automatically issued from the online server, simplicity and high efficiency are realized, manual errors are avoided, and the accuracy is improved.
Description
Technical Field
The invention belongs to the technical field of computers, and particularly relates to a distributed code automatic publishing system and a distributed code automatic publishing method.
Background
The development of the software product is divided into multiple stages, corresponding management tools are required to be used in each stage, but the management tools have a common problem that developers need to learn relevant specifications first and cannot use the relevant specifications immediately after the developers leave the box. Therefore, in the software development cycle, manual intervention is too much in the stages of compiling, publishing and the like, so that the product development is slowed down, the publishing efficiency is low, errors are easy to occur, the management difficulty is high, and the existing codes cannot form closed-loop monitoring after being automatically published, so that the accuracy of code publishing is not high.
Disclosure of Invention
The invention provides a distributed code automatic publishing system and a distributed code automatic publishing method, and aims to solve the problems of slow development, low publishing efficiency, high error probability and high management difficulty in the existing software product development, and low code publishing accuracy caused by the fact that a code cannot form closed-loop monitoring after being automatically published.
In order to achieve the above object, the present invention provides a distributed code automatic publishing system, including:
the monitoring module is used for monitoring at least one bug existing in the running process of a certain project and generating a bug log;
the control module is used for editing the position corresponding to the code of the certain project according to the vulnerability log to obtain a code to be issued;
the test module is used for executing comprehensive test on the code to be issued, and the comprehensive test comprises performance test and function test on the code to be issued;
the packaging module is used for compressing the codes to be issued after the comprehensive test is finished and generating a compressed package file corresponding to the codes to be issued;
and the release module is used for capturing and analyzing the compressed package file corresponding to the code to be released, generating a release code and pushing the generated release code to a server for real automatic release.
Preferably, the comprehensive test comprises:
acquiring the code to be issued, executing a first test, and generating a first test result;
inserting the code to be issued into a position corresponding to the certain project position to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
Preferably, when the first test result and/or the second test result fail, a failed test log is generated and fed back to the control module for a developer to correct the code to be issued.
Preferably, the monitoring module monitors the release code pushed to the server for real automatic release in a preset cycle time.
Preferably, the control module performs distributed code management and control by adopting a gi t tool.
Preferably, the release module adopts a jenkins tool to realize the integration of the release code.
In addition, in order to achieve the above object, the present invention further provides a distributed code automatic publishing method, including:
monitoring at least one vulnerability existing in the running process of a certain project to generate a vulnerability log;
editing a position corresponding to the code of the certain project according to the vulnerability log to obtain a code to be issued;
executing comprehensive tests on the codes to be issued, wherein the comprehensive tests comprise performance tests and function tests on the codes to be issued;
compressing the code to be issued after the comprehensive test is completed, and generating a compressed package file corresponding to the code to be issued;
and capturing and analyzing a compressed package file corresponding to the code to be issued, generating an issuing code, and pushing the generated issuing code to a server for actual automatic issuing.
Preferably, the comprehensive test comprises:
acquiring the code to be issued, executing a first test, and generating a first test result;
inserting the code to be issued into a position corresponding to the certain project position to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
Preferably, when the first test result and/or the second test result fail, a failed test log is generated and fed back to the control module for a developer to correct the code to be issued.
Preferably, the monitoring module monitors the release code pushed to the server for real automatic release in a preset cycle time.
The invention provides a distributed code automatic release system and a method, wherein a vulnerability log is generated by monitoring at least one vulnerability existing in the running process of a certain project, and then the position corresponding to the code of the certain project is edited to obtain the code to be released to execute comprehensive test; compressing the code to be issued after the comprehensive test is completed, and generating a compressed package file corresponding to the code to be issued; and finally, capturing and analyzing the compressed package file corresponding to the code to be issued, generating an issuing code and pushing the issuing code to a server for automatic actual issuing. According to the invention, the control, the test, the packaging and the release are carried out on all links of the software product in the development process, and all links of the software product development can be controlled without manual participation, so that the code release efficiency and the code release accuracy are improved.
To more clearly illustrate the structural features and effects of the present invention, the present invention will be described in detail below with reference to the accompanying drawings and specific embodiments.
Drawings
FIG. 1 is a block diagram of a distributed code automatic distribution system according to a preferred embodiment of the present invention;
FIG. 2 is a flow chart of the distributed code automatic issuing system according to the preferred embodiment of the present invention.
Detailed Description
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the terminology used in the description of the application herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application; the terms "including" and "having," and any variations thereof, in the description and claims of this application and the description of the above figures are intended to cover non-exclusive inclusions. The terms "first," "second," and the like in the description and claims of this application or in the above-described drawings are used for distinguishing between different objects and not for describing a particular order.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
An embodiment of the present invention provides an automatic distributed code publishing system, which is a block diagram of a preferred embodiment of the automatic distributed code publishing system according to the present invention and shown in fig. 1, and includes:
the monitoring module 101 is configured to monitor at least one vulnerability existing in an operation process of a certain project, and generate a vulnerability log.
In an optional embodiment, the developed software product needs to be run and tested, whether a bug is found in the running process of the software product is monitored through setting, and if the bug is found in the running process of the software product, a bug log of the software product is generated for further modification. Wherein the operation of the software product is monitored using Nagios.
Nagios is a free network monitoring tool for opening sources, and can effectively monitor the host states of Windows, Linux and Unix, network equipment such as a switch router and the like. And sending out a mail or short message to alarm when the system or service state is abnormal, informing website operation and maintenance personnel at the first time, and sending out a normal mail or short message after the state is recovered.
And the control module 102 is configured to edit a position corresponding to the code of the certain project according to the vulnerability log to obtain a code to be issued.
In this embodiment, the corresponding position of the software product is searched and located according to the vulnerability log, and the code of the software product at the position is edited, including code modification, addition, and deletion, whether the connection serial port where the code is located is correct, whether the format of the code is correct, and the like.
Further, the control module 102 performs distributed code management using a git tool.
git is an open source distributed version control system, and can effectively process the project version management from very small to very large at high speed.
The test module 103 is configured to perform a comprehensive test on the code to be issued, where the comprehensive test includes a performance test and a function test on the code to be issued.
Specifically, the comprehensive test comprises:
acquiring the code to be issued, executing a first test, and generating a first test result;
inserting the code to be issued into a position corresponding to the certain project position to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
In this embodiment, to ensure that the edited code is correct, the test for the code to be issued needs to be performed twice, where each test includes a performance test and a function test for the code to be issued. The first test is to test the code student, the second test is to test the running of the code in the software product, test the correctness and compatibility of the code edition, and confirm whether the function of the code is displayed.
It should be noted that the performance test includes, but is not limited to, interface connection, code writing or code format, and the like, and the functional test includes, but is not limited to, the function shown by the code to be released, the state of display, the speed of reaction, or a pop-up window, and the like.
Certainly, when the first test result and/or the second test result fail, an early warning is triggered to generate a failed test log, the log records the error place in the code, and the error place is fed back to the control module 102 for the developer to correct, so as to better pass the test and complete the test.
And the packaging module 104 is configured to compress the to-be-issued code after the comprehensive test is completed, and generate a compressed package file corresponding to the to-be-issued code.
In this embodiment, the packaging module 104 may use a maven tool, an Ant tool, or a Gradle tool in the prior art to package and compress the to-be-issued code that completes the comprehensive test into a compressed package file.
And the publishing module 105 is configured to capture and analyze the compressed package file corresponding to the code to be published, generate a publishing code, and push the generated publishing code to a server for real automatic publishing.
In this embodiment, adopt Jenkins instrument to snatch compression package file, analyze out compression package file, generate the release code that waits to release the code and correspond, it is right to realize through Jenkins instrument the integration of release code, the release code is the code through testing success, and later, Jenkins instrument will release code propelling movement to server, and the server just sends out the release code automatically, supplies the software product to demonstrate at the operation in-process.
Furthermore, the monitoring module 101 performs monitoring of a preset period time on the release code pushed to the server for real automatic release, so that continuous monitoring after automatic release of the code is realized, better management perfection is facilitated, and the running efficiency of the software product is improved.
The embodiment of the present invention provides an automatic distributed code publishing method, which is a flowchart of a preferred embodiment of the automatic distributed code publishing system of the present invention, referring to fig. 2, and the method includes:
and S1, monitoring at least one vulnerability existing in the running process of a certain project, and generating a vulnerability log.
In an optional embodiment, the developed software product needs to be run and tested, whether a bug is found in the running process of the software product is monitored through setting, and if the bug is found in the running process of the software product, a bug log of the software product is generated for further modification. Wherein the operation of the software product is monitored using Nagios.
Nagios is a free network monitoring tool for opening sources, and can effectively monitor the host states of Windows, Linux and Unix, network equipment such as a switch router and the like. And sending out a mail or short message to alarm when the system or service state is abnormal, informing website operation and maintenance personnel at the first time, and sending out a normal mail or short message after the state is recovered.
And S2, editing the position corresponding to the code of the certain project according to the vulnerability log to obtain the code to be issued.
In this embodiment, the corresponding position of the software product is searched and located according to the vulnerability log, and the code of the software product at the position is edited, including code modification, addition, and deletion, whether the connection serial port where the code is located is correct, whether the format of the code is correct, and the like.
Further, the step S2 adopts git tool to execute distributed code management and control.
git is an open source distributed version control system, and can effectively process the project version management from very small to very large at high speed.
And S3, executing comprehensive tests on the codes to be issued, wherein the comprehensive tests comprise performance tests and function tests on the codes to be issued.
Specifically, the comprehensive test comprises:
acquiring the code to be issued, executing a first test, and generating a first test result;
inserting the code to be issued into a position corresponding to the certain project position to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
In this embodiment, to ensure that the edited code is correct, the test for the code to be issued needs to be performed twice, where each test includes a performance test and a function test for the code to be issued. The first test is to test the code student, the second test is to test the running of the code in the software product, test the correctness and compatibility of the code edition, and confirm whether the function of the code is displayed.
It should be noted that the performance test includes, but is not limited to, interface connection, code writing or code format, and the like, and the functional test includes, but is not limited to, the function shown by the code to be released, the state of display, the speed of reaction, or a pop-up window, and the like.
Of course, when the first test result and/or the second test result fail, triggering an early warning to generate a failed test log, recording the error location in the code, and feeding back to step S2 for the developer to correct, so as to better pass the test and complete.
S4, compressing the codes to be issued after the comprehensive test is completed, and generating a compressed package file corresponding to the codes to be issued.
In this embodiment, in step S4, a maven tool, an Ant tool, or a Gradle tool in the prior art may be used to package and compress the to-be-issued code that completes the comprehensive test into a compressed package file.
S5, capturing and analyzing the compressed package file corresponding to the code to be issued, generating an issuing code, and pushing the generated issuing code to a server for real automatic issuing.
In this embodiment, adopt Jenkins instrument to snatch compression package file, analyze out compression package file, generate the release code that waits to release the code and correspond, it is right to realize through Jenkins instrument the integration of release code, the release code is the code through testing success, and later, Jenkins instrument will release code propelling movement to server, and the server just sends out the release code automatically, supplies the software product to demonstrate at the operation in-process.
Further, the step S1 performs monitoring of the release code pushed to the server for real automatic release for a preset period of time, so as to realize continuous monitoring after automatic release of the code, which is beneficial to better management and improvement, and improve the efficiency of software product operation.
The technical principle of the present invention has been described above with reference to specific embodiments, which are merely preferred embodiments of the present invention. The protection scope of the present invention is not limited to the above embodiments, and all technical solutions belonging to the idea of the present invention belong to the protection scope of the present invention. Other embodiments of the invention will occur to those skilled in the art without the exercise of inventive faculty, and such will fall within the scope of the invention.
Claims (10)
1. A distributed code automatic publishing system, comprising:
the monitoring module is used for monitoring at least one bug existing in the running process of a certain project and generating a bug log;
the control module is used for editing the position corresponding to the code of the certain project according to the vulnerability log to obtain a code to be issued;
the test module is used for executing comprehensive test on the code to be issued, and the comprehensive test comprises performance test and function test on the code to be issued;
the packaging module is used for compressing the codes to be issued after the comprehensive test is finished and generating a compressed package file corresponding to the codes to be issued;
and the release module is used for capturing and analyzing the compressed package file corresponding to the code to be released, generating a release code and pushing the generated release code to a server for real automatic release.
2. The distributed code automatic release system according to claim 1, characterized in that the comprehensive test comprises:
acquiring the code to be issued, executing a first test, and generating a first test result;
inserting the code to be issued into a position corresponding to the certain project position to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
3. The automatic distributed code publishing system according to claim 2, wherein when the first test result and/or the second test result fails, a failed test log is generated and fed back to the control module for a developer to correct the code to be published.
4. The distributed code automatic issuing system according to claim 1, wherein the monitoring module performs monitoring for a preset cycle time on the issued code that is pushed to a server for real automatic issuing.
5. The system of claim 1, wherein the control module employs a git tool to perform distributed code management.
6. The distributed code automatic release system according to claim 1, wherein the release module employs jenkins tool to realize integration of the release code.
7. A distributed code automatic publishing method is characterized by comprising the following steps:
monitoring at least one vulnerability existing in the running process of a certain project to generate a vulnerability log;
editing a position corresponding to the code of the certain project according to the vulnerability log to obtain a code to be issued;
executing comprehensive tests on the codes to be issued, wherein the comprehensive tests comprise performance tests and function tests on the codes to be issued;
compressing the code to be issued after the comprehensive test is completed, and generating a compressed package file corresponding to the code to be issued;
and capturing and analyzing a compressed package file corresponding to the code to be issued, generating an issuing code, and pushing the generated issuing code to a server for actual automatic issuing.
8. The distributed code automatic release system according to claim 7, characterized in that the comprehensive test comprises:
acquiring the code to be issued, executing a first test, and generating a first test result;
inserting the code to be issued into a position corresponding to the certain project position to execute a second test, and generating a second test result;
and when the first test result and the second test result both pass, completing the test of the code to be issued.
9. The automatic distributed code publishing system according to claim 8, wherein when the first test result and/or the second test result fails, a failed test log is generated and fed back to the control module for a developer to correct the code to be published.
10. The distributed code automatic issuing system according to claim 1, wherein the monitoring module performs monitoring for a preset cycle time on the issued code that is pushed to a server for real automatic issuing.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110310634.7A CN113050982A (en) | 2021-03-23 | 2021-03-23 | Distributed code automatic publishing system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110310634.7A CN113050982A (en) | 2021-03-23 | 2021-03-23 | Distributed code automatic publishing system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113050982A true CN113050982A (en) | 2021-06-29 |
Family
ID=76514676
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110310634.7A Pending CN113050982A (en) | 2021-03-23 | 2021-03-23 | Distributed code automatic publishing system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113050982A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106095415A (en) * | 2016-06-01 | 2016-11-09 | 乐视控股（北京）有限公司 | Exploitation file packing method, Apparatus and system |
| CN107315687A (en) * | 2017-06-29 | 2017-11-03 | 环球智达科技（北京）有限公司 | Code method for automatically releasing |
| CN107450933A (en) * | 2017-08-18 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and system |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
| CN111694592A (en) * | 2020-06-24 | 2020-09-22 | 深圳壹账通智能科技有限公司 | Management method and system for project version release |
| CN112328217A (en) * | 2020-11-03 | 2021-02-05 | 中国平安人寿保险股份有限公司 | Code deployment method, device, system, computer equipment and medium |
-
2021
- 2021-03-23 CN CN202110310634.7A patent/CN113050982A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106095415A (en) * | 2016-06-01 | 2016-11-09 | 乐视控股（北京）有限公司 | Exploitation file packing method, Apparatus and system |
| CN107315687A (en) * | 2017-06-29 | 2017-11-03 | 环球智达科技（北京）有限公司 | Code method for automatically releasing |
| CN107450933A (en) * | 2017-08-18 | 2017-12-08 | 郑州云海信息技术有限公司 | A kind of software continuous integrated approach and system |
| CN109683899A (en) * | 2017-10-18 | 2019-04-26 | 中移(苏州)软件技术有限公司 | A kind of software integrating method and device |
| CN111694592A (en) * | 2020-06-24 | 2020-09-22 | 深圳壹账通智能科技有限公司 | Management method and system for project version release |
| CN112328217A (en) * | 2020-11-03 | 2021-02-05 | 中国平安人寿保险股份有限公司 | Code deployment method, device, system, computer equipment and medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106559270B (en) | Data analysis method and device for urban rail signal equipment | |
| CN107632918B (en) | Monitoring system and method for computing storage equipment | |
| KR100618319B1 (en) | Error test method for mobile communication terminals | |
| CN104503429B (en) | Rail traffic vehicles static test datamation processing method and processing device | |
| CN110096419A (en) | Acquisition methods, interface log management server and the service server of interface log | |
| CN113032262A (en) | Automatic simulation test method | |
| CN107241229A (en) | A kind of business monitoring method and device based on interface testing instrument | |
| CN113946499A (en) | Micro-service link tracking and performance analysis method, system, equipment and application | |
| CN102479152A (en) | Method and device for obtaining tool automatic test results on basis of Android platform | |
| CN113448854A (en) | Regression testing method and device | |
| CN110673873B (en) | Audit-based software release method | |
| CN117421217B (en) | Automatic software function test method, system, terminal and medium | |
| CN109815124B (en) | MBSE-based interlocking function defect analysis method and device and interlocking system | |
| CN109117526A (en) | One kind being suitable for mechanical system maintenance of equipment and guides data record and analysis system | |
| CN113050982A (en) | Distributed code automatic publishing system and method | |
| CN110633199A (en) | Testing apparatus, method, and medium for block chain supporting intelligent contract | |
| CN115587028A (en) | Interface automation test method, system, medium and terminal | |
| CN106294132A (en) | A kind of method and device managing daily record | |
| CN108965053A (en) | Upper computer software method for testing pressure, apparatus and system | |
| CN113495750B (en) | Upgrade detection method and device for equipment and server | |
| JP2014071574A (en) | Log collection method and system | |
| CN112835789A (en) | Realization technology for automatic test of automatic test framework | |
| CN112035356A (en) | Automatic testing method and system for web application compatibility | |
| CN101877874B (en) | The transmission of performance data and output intent, system and equipment | |
| CN105407112B (en) | Equipment capability learning method, device and system |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210629 |