CN114490319A - Distributed continuous integration automatic test method and system - Google Patents
Distributed continuous integration automatic test method and system Download PDFInfo
- Publication number
- CN114490319A CN114490319A CN202111568565.6A CN202111568565A CN114490319A CN 114490319 A CN114490319 A CN 114490319A CN 202111568565 A CN202111568565 A CN 202111568565A CN 114490319 A CN114490319 A CN 114490319A
- Authority
- CN
- China
- Prior art keywords
- test
- code
- automatic
- mirror image
- tool
- 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
- 230000010354 integration Effects 0.000 title claims abstract description 35
- 238000010998 test method Methods 0.000 title claims abstract description 11
- 238000012360 testing method Methods 0.000 claims abstract description 191
- 238000012795 verification Methods 0.000 claims abstract description 42
- 238000000034 method Methods 0.000 claims abstract description 23
- 238000013515 script Methods 0.000 claims abstract description 20
- 230000000391 smoking effect Effects 0.000 claims abstract description 17
- 238000011161 development Methods 0.000 claims abstract description 16
- 238000004519 manufacturing process Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 14
- 230000006870 function Effects 0.000 claims description 9
- 238000001514 detection method Methods 0.000 claims description 8
- BUGBHKTXTAQXES-UHFFFAOYSA-N Selenium Chemical compound [Se] BUGBHKTXTAQXES-UHFFFAOYSA-N 0.000 claims description 6
- 229910052711 selenium Inorganic materials 0.000 claims description 6
- 239000011669 selenium Substances 0.000 claims description 6
- 238000004458 analytical method Methods 0.000 claims description 4
- 150000001875 compounds Chemical class 0.000 claims description 4
- 230000036541 health Effects 0.000 claims description 4
- 238000011056 performance test Methods 0.000 claims description 4
- 238000011076 safety test Methods 0.000 claims description 4
- 238000004806 packaging method and process Methods 0.000 claims description 3
- 238000009781 safety test method Methods 0.000 claims description 2
- 238000010276 construction Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 5
- 230000000694 effects Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012827 research and development Methods 0.000 description 2
- VYZAMTAEIAYCRO-UHFFFAOYSA-N Chromium Chemical compound [Cr] VYZAMTAEIAYCRO-UHFFFAOYSA-N 0.000 description 1
- 241001236644 Lavinia Species 0.000 description 1
- 238000012856 packing Methods 0.000 description 1
- 230000002085 persistent effect 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
- 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
-
- 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/3696—Methods or tools to render software testable
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
- G06F8/63—Image based installation; Cloning; Build to order
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Software Systems (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a distributed continuous integration automatic test method and a system, wherein the method comprises the following steps: the development environment node server acquires codes according to the code paths submitted by the code management tool, packages and compiles the codes, and hooks a code automatic scanning task to perform code normative verification after the compilation is finished; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse; the testing environment node server pulls the mirror image from the Docker mirror image warehouse through the integrated service arrangement tool, and automatically constructs a product testing environment; calling a distributed cloud node server to perform an automation script for smoking test, and then respectively executing a UI automation test and an interface automation test; and after the test is finished, the message notification server automatically generates an automatic test report and sends the automatic test report to the relevant personnel of the project. According to the invention, the compiling construction link and the automatic testing link are respectively operated on different servers, so that the continuous integration efficiency is greatly improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a distributed continuous integration automatic test method and a distributed continuous integration automatic test system based on a micro-service architecture.
Background
Continuous integration of code is a software engineering process, which is a measure for continuously integrating all software engineers working copies of software into the code backbone. Developers frequently integrate code into the backbone throughout the day, and each integration triggers a series of automated processes, as shown in fig. 1, which include compiling, automated testing, deployment, and publishing, etc. In the continuous code integration process, the integration efficiency needs special attention, the faster the code is integrated into the backbone, the shorter the feedback obtaining time of related workers can be, and the more fluent the practical process is.
At present, codes are continuously integrated in practice, and all links in the process, such as a compiling and constructing link and an automatic testing link, are operated on the same server. If the software developed by the micro-service architecture is encountered, the number of micro-services is numerous, the number of automatic tests is huge, the running time of an automatic test link becomes longer, and the speed of obtaining continuous integrated result feedback is slow, so that the software development efficiency is influenced, and the server is always occupied in the process of running the automatic link and cannot respond to other tasks, so that resources cannot be fully utilized.
Disclosure of Invention
The invention aims to provide a distributed continuous integration automatic test method and a distributed continuous integration automatic test system, which are used for solving the problems of long running automatic test time and low continuous integration efficiency in the existing code continuous integration process.
In a first aspect, the present invention provides a distributed continuous integration automation testing method, including the following steps:
s1, the development environment node server acquires the code according to the code path submitted by the code management tool, packages and compiles the code, and after compiling is completed, articulates the code automatic scanning task to carry out code normative verification; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse;
s2, the testing environment node server pulls the mirror image from the Docker mirror image warehouse through the integrated service arrangement tool, and the product testing environment is automatically constructed;
s3, calling the distributed cloud node server to perform an automatic script for smoking test, and respectively executing a UI (user interface) automatic test and an interface automatic test after the smoking test is finished;
and S4, after the test is finished, the message notification server automatically generates an automatic test report and sends the automatic test report to the personnel related to the project.
In a second aspect, the present invention provides a distributed continuous integration automation test system, including:
the development environment node server is used for acquiring codes according to the code paths submitted by the code management tool, packaging and compiling the codes, and hooking a code automatic scanning task to carry out code normative verification after the compiling is finished; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse;
the testing environment node server is used for pulling the mirror image from the Docker mirror image warehouse through an integrated service arranging tool and automatically constructing a product testing environment;
the distributed cloud node server is used for performing an automatic script smoking test firstly and respectively executing a UI (user interface) automatic test and an interface automatic test after the smoking test is finished;
and the message notification server is used for automatically generating an automatic test report after the test is finished and sending the automatic test report to the relevant personnel of the project.
One or more technical solutions provided in the embodiments of the present invention have at least the following technical effects or advantages: and respectively operating a compiling construction link and an automatic testing link on different servers, automatically constructing a product testing environment through a testing environment node server, and performing smoking test, UI automatic test and interface automatic test by adopting a distributed cloud node server. Because the development environment node server is only used for compiling and normative checking of codes and is irrelevant to testing, even if the micro-service number is large and the automatic testing number is large under the micro-service architecture, the rapid feedback of the continuous integration result can be still ensured, and the technical problem that the continuous integration efficiency is lower due to long time for running the automatic testing in the continuous integration process in the prior art is solved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
The invention will be further described with reference to the following examples with reference to the accompanying drawings.
FIG. 1 is a schematic process flow diagram of a prior art software from compiling to deployment and release;
FIG. 2 is a flow chart of a method according to one embodiment of the present invention;
FIG. 3 is a diagram illustrating a distributed architecture for automated testing according to an embodiment of the present invention;
FIG. 4 is a diagram illustrating an automated test report generation status according to an embodiment of the present invention;
FIG. 5 is a schematic interface diagram of the Sonar tool according to the embodiment of the present invention;
FIG. 6 is a schematic flow chart of an embodiment of the present invention during a development phase and a testing phase;
fig. 7 is a schematic structural diagram of a system according to a second embodiment of the present invention.
Detailed Description
The embodiment of the application provides a distributed continuous integration automatic test method and system to solve the problems of long running automatic test time and low continuous integration efficiency in the existing code continuous integration process.
The technical scheme in the embodiment of the application has the following general idea: and respectively operating a compiling construction link and an automatic testing link on different servers, automatically constructing a product testing environment through a testing environment node server, and performing smoking test, UI automatic test and interface automatic test by adopting a distributed cloud node server. The development environment node server is only used for compiling and normative checking of codes, is irrelevant to testing, and is enough to deal with automatic testing under the micro-service architecture with a large number of micro-services, so that the technical problem that in the prior art, the continuous integration efficiency is low due to long time for running the automatic testing in the continuous integration process is solved.
Example one
As shown in fig. 2, the present embodiment provides a distributed continuous integration automation testing method, which includes the following steps:
s1, the development environment node server acquires codes according to the code path submitted by the code management tool, packages and compiles the codes, and hooks a code automatic scanning task to perform code normative verification after the compilation is completed; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse;
s2, the testing environment node server pulls the mirror image from the Docker mirror image warehouse through the integrated service arrangement tool, and the product testing environment is automatically constructed;
s3, as shown in fig. 3, calling the distributed cloud node server to perform the automated script for the smoking test, and after the smoking test is completed, respectively executing the UI automated test and the interface automated test;
s4, as shown in fig. 4, after the test is completed, the message notification server automatically generates an automated test report and sends the automated test report to the personnel related to the project.
As a more preferred or specific implementation manner of this embodiment, the method further includes:
s5, the class production environment node server uses the service arrangement tool to pull the mirror image from the mirror image warehouse, automatically constructs the class production environment, hooks the safety test tool and the performance test tool, verifies the engineering quality and performance, and automatically sends the prompt of the release completion of the class production environment after the verification is completed.
The automatically constructed product test environment specifically comprises:
s21, calling cloud interface deployment service;
and S22, judging whether the service is successfully started through the health check interface, if so, completing the preparation of the test environment and triggering the distributed cloud node server, and if not, feeding back the message of unsuccessful start to development and test personnel.
As shown in fig. 5, in S1, the code normative verification content includes: front-end code normative verification, back-end code normative verification, and unit test JUNIT and the code normative verification is performed using a Sonar tool that provides an interface for "project", "problem", "code rule", "quality configuration", and "quality threshold"; wherein:
the item is used for viewing item information subjected to security scanning;
the question is used for viewing question information of the scanned item;
the code rule is used for setting a rule of code detection;
the quality configuration is used for configuring a rule set used in analysis, and each language has a default configuration;
the "quality threshold" corresponds to a threshold for code detection, and a code problem exceeding the threshold may cause a prompt, or send a mail notification;
in S4, after the feedback result of the automated test report is sent to the relevant personnel of the project, if there is a new function and a relevant Bug, after the testing personnel manually verifies that the new function and the relevant Bug pass, the automated test script is arranged and added to the test case library, and a message is automatically sent to the relevant personnel of the project to prompt the completion of the test release of the product.
The integration service orchestration tool is Docker Compound or k8 s; the UI automatic test uses a Selenium-based test platform Automate, and the interface automatic test uses a Jmeter script and Requests + receiving piling test tool Mock to complete main line flow verification.
In summary, as shown in fig. 6, the task content at different stages of the persistent integration pipeline is clearly described:
first, research and development stage
Before submitting the codes, the research and development personnel use the Sonar related plug-in to scan the codes and submit the code management tool git after the modification is completed;
second, testing stage
The development environment node server acquires submitted code paths from git by using a Jenkins task arranging tool, a Junit test is started in the compiling process through Maven packing and compiling, after compiling is completed, a code automatic scanning task is hooked to perform code normative verification, a Docker mirror image file is created after the tool passes the Sonar code normative check, and the Docker mirror image file is pushed to a Docker mirror image warehouse;
the testing environment node server pulls the mirror image from the mirror image warehouse through an integrated service orchestration tool Docker complex or k8s, automatically constructs a product testing environment, triggers an automatic testing node server, performs smoking test through an automatic script, and after the test is completed, the testing work is divided into two parts:
(1) and respectively executing UI (user interface) automatic test and interface automatic test by the two cloud node servers, wherein the UI automatic test uses a Selenium-based test platform Automate, and the interface automatic test uses a Jmeter script and Requests + receiving piling test tool Mock to complete main line flow verification. After the code is compiled and packaged, the test Server is triggered and called and is responsible for managing and calling two distributed cloud servers, wherein one Windows Server uses a UI automatic test platform Automate which is independently developed based on the Selenium to provide support for browsers such as Chrome, Firefox, IE and phantomJS which are common in the market and execute UI test; another Linux server is responsible for running a jmeter interface test script and requests library based interface test code written in python language. After the test is finished, the test result is fed back to related personnel through the mail, and follow-up work is carried out.
(2) The tester manually verifies the new functions and the related bugs, arranges the automatic test scripts and adds the automatic test scripts into a test case library after the test is passed, automatically sends a prompt mail after the verification is finished, and the product test release is finished;
thirdly, deployment phase:
when a product releases a large edition, safety test and performance test need to be carried out in a class production environment, the class production environment is built as much as possible according to the production environment, the system comprises a network, data volume, service deployment topology and the like, a class production environment node server uses a service arrangement tool to pull a mirror image from a mirror image warehouse, the class production environment is automatically built, the mirror image is pulled from the mirror image warehouse through a Jenkins integration Docker complex or K8s, the integrated test environment is automatically built, the Jenkins hitches the safety test tool and the performance test tool, the engineering quality and the performance are verified, a prompt mail is automatically sent after verification is completed, and the class production environment is released completely.
Based on the same inventive concept, the application also provides a device corresponding to the method in the first embodiment, which is detailed in the second embodiment.
Example two
As shown in fig. 7, in this embodiment, a distributed continuous integrated automation test system is provided, which includes:
the development environment node server is used for acquiring codes according to the code paths submitted by the code management tool, packaging and compiling the codes, and after compiling is completed, hooking a code automatic scanning task to carry out code normative verification; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse;
the testing environment node server is used for pulling the mirror image from the Docker mirror image warehouse through the integrated service arrangement tool and automatically constructing a product testing environment;
the distributed cloud node server is used for performing an automatic script smoking test firstly and respectively executing a UI (user interface) automatic test and an interface automatic test after the smoking test is finished;
and the message notification server is used for automatically generating an automatic test report after the test is finished and sending the automatic test report to the relevant personnel of the project.
As a more preferred or specific implementation manner of this embodiment, the apparatus further includes:
the class production environment node server is used for pulling the mirror image from the mirror image warehouse through the service arrangement tool and automatically constructing a class production environment; and hanging a safety testing tool and a performance testing tool, verifying the engineering quality and performance, and automatically sending a prompt of completion of release of the production environment after verification is completed.
The specific process for automatically constructing the product test environment comprises the following steps: calling a cloud interface deployment service; and judging whether the service is successfully started or not through the health check interface, if so, completing the preparation of the test environment and triggering the distributed cloud node server, and if not, feeding back a message of unsuccessful start to development and testing personnel.
The code normative verification content comprises the following steps: front-end code normative verification, back-end code normative verification, and unit test JUNIT and the code normative verification is performed using a Sonar tool that provides an interface for "project", "problem", "code rule", "quality configuration", and "quality threshold"; wherein:
the item is used for viewing item information subjected to security scanning;
the question is used for viewing question information of the scanned item;
the code rule is used for setting a rule of code detection;
the quality configuration is used for configuring a rule set used in analysis, and each language has a default configuration;
the "quality threshold" corresponds to a threshold for code detection, and a code problem exceeding the threshold may cause a prompt, or send a mail notification;
after the information notification server sends the feedback result of the automated test report to the relevant personnel of the project, if a new function and a relevant Bug exist, after the testing personnel manually verifies that the new function and the relevant Bug pass, the automatic test script is arranged and added into the test case library, and the information notification server automatically sends information to the relevant personnel of the project to prompt the completion of the test release of the product.
The integration service orchestration tool is Docker Compound or k8 s; the UI automatic test uses a Selenium-based test platform Automate, and the interface automatic test uses a Jmeter script and Requests + receiving piling test tool Mock to complete main line flow verification.
Since the system described in the second embodiment of the present invention is a system used for implementing the method of the first embodiment of the present invention, a person skilled in the art can understand the specific structure and the deformation of the device based on the method described in the first embodiment of the present invention, and thus the detailed description is omitted here. All the devices adopted in the method of the first embodiment of the present invention belong to the protection scope of the present invention.
The technical scheme provided in the embodiment of the application at least has the following technical effects or advantages: and respectively operating a compiling construction link and an automatic testing link on different servers, automatically constructing a product testing environment through a testing environment node server, and performing smoking test, UI automatic test and interface automatic test by adopting a distributed cloud node server. Because the development environment node server is only used for compiling and normative checking of codes and is irrelevant to testing, even if the micro-service number is large and the automatic testing number is large under the micro-service architecture, the rapid feedback of the continuous integration result can be still ensured, and the technical problem that the continuous integration efficiency is lower due to long time for running the automatic testing in the continuous integration process in the prior art is solved.
Although specific embodiments of the invention have been described above, it will be understood by those skilled in the art that the specific embodiments described are illustrative only and are not limiting upon the scope of the invention, and that equivalent modifications and variations can be made by those skilled in the art without departing from the spirit of the invention, which is to be limited only by the appended claims.
Claims (10)
1. A distributed continuous integration automatic test method is characterized in that: the method comprises the following steps:
s1, the development environment node server acquires codes according to the code path submitted by the code management tool, packages and compiles the codes, and hooks a code automatic scanning task to perform code normative verification after the compilation is completed; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse;
s2, the testing environment node server pulls the mirror image from the Docker mirror image warehouse through the integrated service arrangement tool, and the product testing environment is automatically constructed;
s3, calling the distributed cloud node server to perform an automatic script for smoking test, and after the smoking test is finished, respectively executing a UI (user interface) automatic test and an interface automatic test;
and S4, after the test is finished, the message notification server automatically generates an automatic test report and sends the automatic test report to the personnel related to the project.
2. The distributed continuous integrated automation test method of claim 1, characterized in that: further comprising:
and S5, the class production environment node server uses the service arrangement tool to pull the mirror image from the mirror image warehouse, automatically constructs the class production environment, hooks the safety test tool and the performance test tool, verifies the engineering quality and performance, and automatically sends a prompt of completing the release of the class production environment after the verification is completed.
3. The distributed continuous integrated automation test method of claim 1, characterized in that: the automatically constructed product test environment specifically comprises:
s21, calling cloud interface deployment service;
and S22, judging whether the service is successfully started through the health check interface, if so, completing the preparation of the test environment and triggering the distributed cloud node server, and if not, feeding back the message of unsuccessful start to development and test personnel.
4. The distributed continuous integrated automation test method of claim 1, characterized in that: in S1, the code normative verification content includes: front-end code normative verification, back-end code normative verification, and unit test JUNIT and the code normative verification is performed using a Sonar tool that provides an interface for "project", "problem", "code rule", "quality configuration", and "quality threshold"; wherein:
the item is used for viewing item information subjected to security scanning;
the question is used for viewing question information of the scanned item;
the code rule is used for setting a rule of code detection;
the quality configuration is used for configuring a rule set used in analysis, and each language has a default configuration;
the "quality threshold" corresponds to a threshold for code detection, and a code problem exceeding the threshold may cause a prompt, or send a mail notification;
in S4, after the feedback result of the automated test report is sent to the relevant personnel of the project, if there is a new function and a relevant Bug, after the testing personnel manually verifies that the new function and the relevant Bug pass, the automated test script is arranged and added to the test case library, and a message is automatically sent to the relevant personnel of the project to prompt the completion of the test release of the product.
5. The distributed continuous integrated automation test method of claim 1 or 2, characterized in that: the integration service orchestration tool is Docker Compound or k8 s; the UI automatic test uses a Selenium-based test platform Automate, and the interface automatic test uses a Jmeter script and Requests + receiving piling test tool Mock to complete main line flow verification.
6. The utility model provides a distributed automation test system that continues to integrate which characterized in that: the method comprises the following steps:
the development environment node server is used for acquiring codes according to the code paths submitted by the code management tool, packaging and compiling the codes, and hooking a code automatic scanning task to carry out code normative verification after the compiling is finished; after code normative verification is passed, a Docker mirror image file is created and pushed to a Docker mirror image warehouse;
the testing environment node server is used for pulling the mirror image from the Docker mirror image warehouse through an integrated service arranging tool and automatically constructing a product testing environment;
the distributed cloud node server is used for performing an automatic script smoking test firstly and respectively executing a UI (user interface) automatic test and an interface automatic test after the smoking test is finished;
and the message notification server is used for automatically generating an automatic test report after the test is finished and sending the automatic test report to the relevant personnel of the project.
7. The distributed continuous integrated automation test system of claim 6, wherein: further comprising:
the class production environment node server is used for pulling the mirror image from the mirror image warehouse through the service arrangement tool and automatically constructing a class production environment; and hanging a safety testing tool and a performance testing tool, verifying the engineering quality and performance, and automatically sending a prompt of completion of release of the production environment after verification is completed.
8. The distributed continuous integrated automation test system of claim 6, wherein: the specific process for automatically constructing the product test environment comprises the following steps: calling a cloud interface deployment service; and judging whether the service is successfully started or not through the health check interface, if so, completing the preparation of the test environment and triggering the distributed cloud node server, and if not, feeding back a message of unsuccessful start to development and testing personnel.
9. The distributed continuous integrated automation test system of claim 6, wherein: the code normative verification content comprises the following steps: front-end code normative verification, back-end code normative verification, and unit test JUNIT and the code normative verification is performed using a Sonar tool that provides an interface for "project", "problem", "code rule", "quality configuration", and "quality threshold"; wherein:
the item is used for viewing item information subjected to security scanning;
the question is used for viewing question information of the scanned item;
the code rule is used for setting a rule of code detection;
the quality configuration is used for configuring a rule set used in analysis, and each language has a default configuration;
the "quality threshold" corresponds to a threshold for code detection, and a code problem exceeding the threshold may cause a prompt, or send a mail notification;
after the information notification server sends the feedback result of the automated test report to the relevant personnel of the project, if a new function and a relevant Bug exist, after the testing personnel manually verifies that the new function and the relevant Bug pass, the automatic test script is arranged and added into the test case library, and the information notification server automatically sends information to the relevant personnel of the project to prompt the completion of the test release of the product.
10. The distributed continuous integrated automation test system of claim 6 or 7, wherein: the integration service orchestration tool is Docker Compound or k8 s; the UI automatic test uses a Selenium-based test platform Automate, and the interface automatic test uses a Jmeter script and Requests + receiving piling test tool Mock to complete main line flow verification.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111568565.6A CN114490319A (en) | 2021-12-21 | 2021-12-21 | Distributed continuous integration automatic test method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111568565.6A CN114490319A (en) | 2021-12-21 | 2021-12-21 | Distributed continuous integration automatic test method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114490319A true CN114490319A (en) | 2022-05-13 |
Family
ID=81494758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111568565.6A Pending CN114490319A (en) | 2021-12-21 | 2021-12-21 | Distributed continuous integration automatic test method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114490319A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115034095A (en) * | 2022-08-10 | 2022-09-09 | 国网江苏省电力有限公司信息通信分公司 | Sensitive state research and development simulation system |
| CN115509544A (en) * | 2022-11-22 | 2022-12-23 | 成都佰维存储科技有限公司 | NVME continuous integration method and device, readable storage medium and electronic equipment |
| CN116400987A (en) * | 2023-06-06 | 2023-07-07 | 智者四海（北京）技术有限公司 | Continuous integration method, device, electronic equipment and storage medium |
| CN117354208A (en) * | 2023-09-28 | 2024-01-05 | 广州翼辉信息技术有限公司 | CI/CD-based automatic test method and system for CODESYS bus protocol stack |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109710524A (en) * | 2018-12-19 | 2019-05-03 | 上海华兴数字科技有限公司 | A kind of automatic test approach, system and computer storage medium |
| CN110209421A (en) * | 2019-05-23 | 2019-09-06 | 北京奥鹏远程教育中心有限公司 | For educating the automation continuous integrating management method of cloud platform |
| CN111198814A (en) * | 2019-12-23 | 2020-05-26 | 曙光信息产业(北京)有限公司 | Continuously integrated acceptance system for continuous delivery |
| CN111552644A (en) * | 2020-04-28 | 2020-08-18 | 成都库珀区块链科技有限公司 | Micro-service architecture-based software continuous integration method |
| CN112100051A (en) * | 2020-07-30 | 2020-12-18 | 江苏清微智能科技有限公司 | Automatic smoking test system and test method thereof |
| CN112765043A (en) * | 2021-03-16 | 2021-05-07 | 上饶市中科院云计算中心大数据研究院 | Automatic testing method and device based on docker |
| CN112988594A (en) * | 2021-04-25 | 2021-06-18 | 郑州信大捷安信息技术股份有限公司 | Integrated detection method and system for code quality evaluation |
| CN113703730A (en) * | 2021-08-30 | 2021-11-26 | 平安普惠企业管理有限公司 | Continuous integration method and device, computer equipment and storage medium |
-
2021
- 2021-12-21 CN CN202111568565.6A patent/CN114490319A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109710524A (en) * | 2018-12-19 | 2019-05-03 | 上海华兴数字科技有限公司 | A kind of automatic test approach, system and computer storage medium |
| CN110209421A (en) * | 2019-05-23 | 2019-09-06 | 北京奥鹏远程教育中心有限公司 | For educating the automation continuous integrating management method of cloud platform |
| CN111198814A (en) * | 2019-12-23 | 2020-05-26 | 曙光信息产业(北京)有限公司 | Continuously integrated acceptance system for continuous delivery |
| CN111552644A (en) * | 2020-04-28 | 2020-08-18 | 成都库珀区块链科技有限公司 | Micro-service architecture-based software continuous integration method |
| CN112100051A (en) * | 2020-07-30 | 2020-12-18 | 江苏清微智能科技有限公司 | Automatic smoking test system and test method thereof |
| CN112765043A (en) * | 2021-03-16 | 2021-05-07 | 上饶市中科院云计算中心大数据研究院 | Automatic testing method and device based on docker |
| CN112988594A (en) * | 2021-04-25 | 2021-06-18 | 郑州信大捷安信息技术股份有限公司 | Integrated detection method and system for code quality evaluation |
| CN113703730A (en) * | 2021-08-30 | 2021-11-26 | 平安普惠企业管理有限公司 | Continuous integration method and device, computer equipment and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 周有志: ""基于云计算分布式系统性能测试技术研究与应用"", 《中国优秀硕士学位论文全文数据库信息科技辑》 * |
| 周有志: ""基于云计算分布式系统性能测试技术研究与应用"", 《中国优秀硕士学位论文全文数据库信息科技辑》, no. 12, 15 December 2015 (2015-12-15), pages 4 * |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115034095A (en) * | 2022-08-10 | 2022-09-09 | 国网江苏省电力有限公司信息通信分公司 | Sensitive state research and development simulation system |
| CN115034095B (en) * | 2022-08-10 | 2022-11-04 | 国网江苏省电力有限公司信息通信分公司 | Sensitive state research and development simulation system |
| CN115509544A (en) * | 2022-11-22 | 2022-12-23 | 成都佰维存储科技有限公司 | NVME continuous integration method and device, readable storage medium and electronic equipment |
| CN115509544B (en) * | 2022-11-22 | 2023-03-21 | 成都佰维存储科技有限公司 | NVME continuous integration method and device, readable storage medium and electronic equipment |
| CN116400987A (en) * | 2023-06-06 | 2023-07-07 | 智者四海（北京）技术有限公司 | Continuous integration method, device, electronic equipment and storage medium |
| CN116400987B (en) * | 2023-06-06 | 2023-08-18 | 智者四海（北京）技术有限公司 | Continuous integration method, device, electronic equipment and storage medium |
| CN117354208A (en) * | 2023-09-28 | 2024-01-05 | 广州翼辉信息技术有限公司 | CI/CD-based automatic test method and system for CODESYS bus protocol stack |
| CN117354208B (en) * | 2023-09-28 | 2024-04-16 | 广州翼辉信息技术有限公司 | Automatic CODESYS bus protocol stack testing method and system based on CI/CD |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114490319A (en) | Distributed continuous integration automatic test method and system | |
| CN109960643B (en) | Code testing method and device | |
| Sneha et al. | Research on software testing techniques and software automation testing tools | |
| US8359581B2 (en) | Automatic collection of diagnostic traces in an automation framework | |
| CN111414172B (en) | Automatic deployment and release system and method for application software | |
| WO2020140820A1 (en) | Software testing method, system, apparatus, device, medium, and computer program product | |
| US10678666B1 (en) | Method and system for implementing automated test and retest procedures in a virtual test environment | |
| Xu et al. | POD-Diagnosis: Error diagnosis of sporadic operations on cloud applications | |
| Amalfitano et al. | A toolset for gui testing of android applications | |
| CN105701010A (en) | Method and device for accelerating software testing | |
| CN110765018B (en) | Automatic interface testing method and equipment | |
| JP2010231782A (en) | Method and system for function automation | |
| CN104636251B (en) | A kind of more browser compatibility method of testings and system | |
| CN112241360A (en) | Test case generation method, device, equipment and storage medium | |
| CN114297056A (en) | Automatic testing method and system | |
| CN110727575A (en) | Information processing method, system, device and storage medium | |
| CN114297666A (en) | Cloud deployment automation vulnerability mining system based on fuzzy test | |
| CN114168213A (en) | Software release method and device based on Jenkins and electronic equipment | |
| US9026997B2 (en) | Systems and methods for executing object-oriented programming code invoking pre-existing objects | |
| CN110543429A (en) | Test case debugging method and device and storage medium | |
| Abdul et al. | Implementing Continuous Integration towards rapid application development | |
| CN115061746A (en) | Jenkins-based vehicle-mounted network controller product development method and system | |
| CN112035356B (en) | Automatic testing method and system for web application compatibility | |
| CN114385258A (en) | Automatic testing method and device, electronic equipment and storage medium | |
| Aho et al. | Continuous piloting of an open source test automation tool in an industrial environment |
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 | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20220513 |