CN111324522A - Automatic test system and method - Google Patents
Automatic test system and method Download PDFInfo
- Publication number
- CN111324522A CN111324522A CN201811525198.XA CN201811525198A CN111324522A CN 111324522 A CN111324522 A CN 111324522A CN 201811525198 A CN201811525198 A CN 201811525198A CN 111324522 A CN111324522 A CN 111324522A
- Authority
- CN
- China
- Prior art keywords
- test
- software
- source code
- module
- tested
- 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
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/368—Test management for test version control, e.g. updating test cases to a new software version
-
- 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/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses an automatic test system and method. The disclosed system comprises: the source code management module is used for carrying out version management on a source code of the software to be tested; the testing environment constructing module is used for constructing a testing environment of the software to be tested based on the source code of the software to be tested; the automatic generation module of the test case and the test script is used for automatically generating the test case and the test script based on the test operation executed by the user through the GUI; and the test module is used for automatically executing the test and generating a test report under the test environment based on the test case and the test script. The technical scheme disclosed reduces the manual operation steps in the automatic testing process, shortens the life cycle of software development and reduces the complexity of software product maintenance.
Description
Technical Field
The invention relates to the field of automatic testing, in particular to an automatic testing system and method.
Background
After the application software is developed, various tests such as a function test, a performance test and the like are generally required, and the application software can be issued to a user for use only after the tests are passed. Thus, software testing is an important stage in the lifecycle of a software project.
Taking web software development as an example, developers usually perform front-end and back-end development respectively to improve development efficiency. After the development is completed, front-end page testing and back-end business function testing are usually required. The front-end and back-end are interdependent on each other, one having a problem and the other possibly requiring a corresponding source code adjustment. For example, after web software development is completed, a tester needs to plan a test case of each function point to be tested, then writes corresponding test script codes according to the test case, coordinates operation and maintenance personnel to prepare a test environment after completion, and needs to collect and summarize test results and feed back the summarized test results to the developer after the test script is run.
With the increasingly prominent requirements of fast iteration and fast delivery in the development process, in the process of fast iteration of the project, a test is inevitably carried out once and again in order to ensure the delivery quality. If the manual test is carried out, the labor is wasted. For example, performing front-end or back-end tests alone does not cover a high degree and it is highly likely that some of the test sessions will be ignored by human error. When the problem is detected, the tester and the developer need to communicate closely to solve the problem, so that a great deal of manpower, material resources and time are wasted. Therefore, manual testing has not been able to meet the testing requirements of large software, and automated testing techniques have emerged.
However, the existing automated testing tools or software can only complete a part of the whole testing work, and the testing process usually requires a lot of manual operations of professional testers and operation and maintenance personnel. For example, an automatic recording tool can only record and generate a test script automatically, and since the front-end technology is changed day by day, a professional tester is usually required to write many test cases to perform an automatic test with a test coverage rate meeting the requirement by combining the test script. Test cases also need to be updated frequently as new functionality is developed. For example, a separate test environment deployment tool is required for the operation and maintenance personnel to deploy the test environment and to maintain software updates within the test environment. Moreover, similar to manual testing, the problem testing requires close communication between the tester and the developer to solve the problem, which also results in a great deal of waste of manpower, material resources and time. Thus, existing automated test tools have also failed to meet the need.
Therefore, in order to reduce manual operation steps in the automatic testing process, shorten the life cycle of software development, reduce the workload of development and testing personnel, and reduce the complexity of software product maintenance, a new technical scheme needs to be provided.
Disclosure of Invention
The automated test system according to the present invention comprises:
the source code management module is used for carrying out version management on a source code of the software to be tested;
the testing environment constructing module is used for constructing a testing environment of the software to be tested based on the source code of the software to be tested;
the automatic generation module of the test case and the test script is used for automatically generating the test case and the test script based on the test operation executed by the user through the GUI;
and the test module is used for automatically executing the test and generating a test report under the test environment based on the test case and the test script.
The automatic test system according to the invention further comprises:
and the software release module is used for automatically releasing the software which passes the automatic test.
According to the automatic test system of the invention, the source code management module is further used for:
the source code update message is automatically sent based on webhook,
the test environment construction module is also used for:
receiving a source code updating message based on webhook, downloading and recompiling the updated source code, reconstructing a testing environment of the software to be tested,
wherein the source code management module comprises one of the following: SVN, Gitlab, and the test environment construction module comprises Jenkins.
According to the automatic test system of the invention, the test case and test script automatic generation module is further used for:
automatically generating test cases and test scripts by recording test operations executed by a user through a GUI,
the automatic generation module of the test case and the test script comprises a Selenium.
According to the automatic test system of the invention, the test environment construction module is further used for:
constructing a Docker mirror image of the software to be tested and/or the web browser software based on a Docker virtualization technology, further constructing a virtual test environment of the software to be tested,
the testing environment building module comprises Jenkins, and the web browser software comprises Chrome web browser software in a Chrome-header mode.
The automatic test method comprises the following steps:
using a source code management module to perform version management on a source code of software to be tested;
constructing a test environment of the software to be tested based on a source code of the software to be tested by using a test environment construction module;
automatically generating a test case and a test script based on a test operation executed by a user through a GUI (graphical user interface) by using a test case and test script automatic generation module;
and automatically executing the test and generating a test report under the test environment by using the test module based on the test case and the test script.
The automatic test method further comprises the following steps:
and automatically releasing the software passing the automatic test by using a software release module.
The automatic test method further comprises the following steps:
automatically sending source code update messages based on webhook by using a source code management module;
using a test environment construction module to receive a source code updating message based on webhook, downloading and recompiling the updated source code, reconstructing the test environment of the software to be tested,
wherein the source code management module comprises one of the following: SVN, Gitlab, and the test environment construction module comprises Jenkins.
The automatic test method further comprises the following steps:
the test case and the test script are automatically generated by using the test case and test script automatic generation module through recording the test operation executed by the user through the GUI,
the automatic generation module of the test case and the test script comprises a Selenium.
The automatic test method further comprises the following steps:
constructing a Docker mirror image of the software to be tested and/or the web browser software based on a Docker virtualization technology by using a test environment construction module so as to construct a virtual test environment of the software to be tested,
the testing environment building module comprises Jenkins, and the web browser software comprises Chrome web browser software in a Chrome-header mode.
According to the technical scheme of the invention, the manual operation steps in the automatic test process are reduced, the life cycle of software development is shortened, and the complexity of software product maintenance is reduced.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention. In the drawings, like reference numerals are used to indicate like elements. The drawings in the following description are directed to some, but not all embodiments of the invention. For a person skilled in the art, other figures can be derived from these figures without inventive effort.
FIG. 1 schematically shows a block schematic of an automated test system according to the present invention.
Fig. 2 shows a schematic flow diagram of an automated testing method according to the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention. It should be noted that the embodiments and features of the embodiments in the present application may be arbitrarily combined with each other without conflict.
FIG. 1 schematically shows a block schematic of an automated test system according to the present invention.
As shown in the solid line box of fig. 1, the automated test system 100 according to the present invention includes:
the source code management module 101 is used for performing version management on a source code of software to be tested;
the testing environment constructing module 103 is used for constructing a testing environment of the software to be tested based on the source code of the software to be tested;
a test case and test script automatic generation module 105, configured to automatically generate a test case and a test script based on a test operation performed by a user through a GUI;
and the test module 107 is used for automatically executing the test and generating a test report under the test environment based on the test case and the test script.
For example, the test environment described above is consistent with the actual environment in which the user is using the software.
Optionally, as shown in the dashed box of fig. 1, the automated testing system 100 further includes:
and the software release module 109 is used for automatically releasing the software which passes the automatic test.
For example, the executable file after compiling and linking can be automatically published after being packaged.
For example, when the software to be tested fails the above automatic test, the result of the test failure is reported to the developer, at this time, the developer needs to modify the source code, submit the updated source code to the source code management module 101, and re-execute the next round of automatic test.
Optionally, the source code management module 101 is further configured to:
the source code update message is automatically sent based on webhook,
the test environment construction module 103 is further configured to:
receiving a source code updating message based on webhook, downloading and recompiling the updated source code, reconstructing a testing environment of the software to be tested,
wherein the source code management module 101 includes one of the following: SVN, Gitlab, test environment construction module 103 includes Jenkins.
For example, when a code repository (e.g., SVN, gillab) in the source code management module 101 has operations of pushing, submitting, pulling, branching, merging, and the like, Jenkins in the test environment construction module 103 may be automatically notified through webhook, and NoCI (i.e., non-persistent integration) checking, printing information, software compiling, linking, packaging, copying to a destination computer (e.g., an anchor host), deploying to a development environment, deploying to a test environment, deploying to a platform (stage), deploying to prod, deploying to a shell environment, uploading to a storage server, obtaining a final output result, ending, and the like (the above operations may be customized according to different software to be tested or different specific test requirements), and constructing a software package of the latest code without active triggering of a client (i.e., a front end).
For example, a developer may add remark information when submitting code, and the remark information may include a custom (e.g., composed of some special characters) identifier for instructing the test environment construction module 103 not to perform automatic construction and test operations on the code. Thus, if the NoCI condition is met (i.e., the remark information contains the custom identification described above) after the NoCI check is performed, automated build and test operations on these codes are not triggered.
For example, Jenkins provides information on whether each related operation in the build process was successfully performed.
Optionally, the Jenkins software may automatically send the construction result (for example, the information of success or failure in construction) of the software package to the Slack communication software, and a developer may directly obtain the information of success in construction of the software package or the warning information of failure in construction through the Slack communication software without manually querying the construction result in Jenkins.
Optionally, the test case and test script automatic generation module 105 is further configured to:
automatically generating test cases and test scripts by recording test operations executed by a user through a GUI,
the automatic test case and test script generation module 105 includes a Selenium.
For example, when the function of the software to be tested is changed (for example, a new function is added) or when the test is first tested, the following specific steps are performed to implement the test operation performed by the recording user of the test case and test script automatic generation module 105 through the GUI, and the above functions of the test case and test script are automatically generated:
a non-professional tester only needs to simulate the operation performed by a real user on a web page in the test environment, where the test case (e.g., in the form of a plug-in) and test script automatic generation module 105 may automatically capture web page elements (e.g., forms, buttons, menus, etc.), record the operation performed by the user on different web page elements (e.g., clicking, keyboard input, selecting options, etc.), and automatically generate test script codes (e.g., including test cases) according to the operation corresponding to the web page elements after the recording is completed.
For example, taking a user login page containing two text input boxes of "username" and "password" and a "login" button as an example, to test the user login operation function of the software, the following recording operation may be performed:
1. a landing page (e.g., http:// www.testlogin.com) is opened.
2. A user name (username) is entered.
3. A password (password) is entered.
3. Click the login button.
For the four operation steps, the recorded specific operation information is shown in table 1:
table 1 specific operation information recorded
| Operating commands | Operation object | Variables corresponding to web page elements |
| open | http://www.testlogin.com | |
| type | id＝email | username |
| type | id＝password | password |
| click | //button[@type＝’submit’] |
At least one of test script codes such as python, C #, Java, Ruby, Groovy and Robot Framework is generated, wherein the python code automatically generated at this time is as follows:
def test_login(self):
driver＝self.driver
driver.get(“http://www.testlogin.com”)
driver.find_element_by_id(“email”).clear()
driver.find_element_by_id(“email”).send_keys(“username”)
driver.find_element_by_id(“password”).clear()
driver.find_element_by_id(“password”).send_keys(“password”)
driver.find_element_by_xpath(“//button[@type＝’submit’]”).click()
all operation steps in the automatically generated code can be independently modified and deleted, and new steps can be manually added into the code.
Optionally, the test environment construction module 103 is further configured to:
the method comprises the steps of constructing a Docker mirror image of software to be tested and/or web browser software based on a Docker virtualization technology, and further constructing a virtual test environment (including a mirror image/container environment of the software to be tested) of the software to be tested, wherein a test environment construction module 103 comprises Jenkins, and the web browser software comprises Chrome web browser software in a Chrome-header mode.
For example, after detecting that a software package of the software to be tested is successfully constructed, the Jenkins software module in the test environment construction module 103 may trigger a manufacturing process of a Docker image of the software (project) to be tested, and automatically start a container environment of the software project after the manufacturing is successful, and for a software project with higher complexity, also support the construction of multiple Docker images and do Docker organization based on Docker-complex. The step firstly ensures the data consistency during each automatic test, and is triggered by Jenkins, thereby reducing the operation and maintenance cost.
At this time, information that the software package of the software to be tested is successfully constructed can be automatically notified to Jenkins in the testing environment construction module 103 through webhook, and operations such as updating files on the infrastructure host, creating an installer (installer), constructing a Docker image, constructing a package folder of the Docker image, executing front-end testing and the like are triggered without the need of active triggering of the client.
In addition, the test environment construction module 103 can also be used for automatic production of a Docker image of web browser software.
For example, Jenkins may provide information on whether each relevant operation in the Docker image production process (e.g., loading a dependency file of an image, loading a start script file, etc.) was executed successfully.
For example, in order to run tests on an unbounded server, e.g., a persistent integration (CI) server and reduce external interference, ensure test stability and facilitate operation and maintenance, a Chrome browser using a containerized Chrome-header mode may be required.
However, default Docker authority may cause failure of starting the Chrome-header mode, and the "cap-add" parameter setting may give too many unnecessary authorities to the Chrome-header mode, which affects system security. Therefore, to make a container for Chrome-browser software in Chrome-header mode and to coordinate with the test environment, the following improvements are needed in addition to compiling installation.
Debugging the Chrome-thread mode learns that the Chrome-thread needs to call the following system functions: arch _ prctl (), chrome (), clone (), fanotify _ init (), name _ to _ handle _ at (), open _ by _ handle _ at (), setdomainname (), sethostname (), syslog (), unshare (), vhangup (), setns ().
Therefore, the security mechanism of seccomp can be used to limit the system call authority of Chrome-header in cooperation with the parameter setting of sec kernel-opt seccomp $ HOME/Chrome. And then two kinds of software, namely ChromeDriver and Selenium, are installed in the Docker.
When testing a server without an interface by combining a Chrome browser in a Chrome-browser mode, Jenkins in the test environment building module 103 is further used for executing the following operations:
1. jenkins automatically starts a Chrome-header container and mounts a test script directory.
The operation not only clears the cache, cookie, application data and other factors of the client executing the test, which may influence the test result, but also greatly reduces the destruction overhead compared with the establishment of the virtual machine client due to the characteristics of the container.
2. And after detecting that the Chrome-header container is successfully started, entering the container to execute the test script, and automatically generating a test report.
Because the recording tool (e.g., Selenium) itself supports the selenie command, a test report can be automatically generated by this operation after the test script is executed. The test report can record each step and data of the test script, detailed debugging information related to each error step and screenshots of the error page in detail.
3. And automatically verifying whether the test is passed, namely delivering when the test is passed, and sending alarm information to developers when the test is not passed.
Fig. 2 shows a schematic flow diagram of an automated testing method according to the invention.
As shown in the solid line box of fig. 2, the automated testing method according to the present invention includes:
step S202: using a source code management module to perform version management on a source code of software to be tested;
step S204: constructing a test environment of the software to be tested based on a source code of the software to be tested by using a test environment construction module;
step S206: automatically generating a test case and a test script based on a test operation executed by a user through a GUI (graphical user interface) by using a test case and test script automatic generation module;
step S208: and automatically executing the test and generating a test report under the test environment by using the test module based on the test case and the test script.
Optionally, as shown in the dashed box of fig. 2, the automated testing method according to the present invention further includes:
step S210: and automatically releasing the software passing the automatic test by using a software release module.
Optionally, as shown in the dashed box of fig. 2, the automated testing method according to the present invention further includes:
step S212: automatically sending source code update messages based on webhook by using a source code management module;
step S214: using a test environment construction module to receive a source code updating message based on webhook, downloading and recompiling the updated source code, reconstructing the test environment of the software to be tested,
wherein the source code management module comprises one of the following: SVN, Gitlab, and the test environment construction module comprises Jenkins.
Optionally, as shown in the dashed box of fig. 2, the automated testing method according to the present invention further includes:
step S216: the test case and the test script are automatically generated by using the test case and test script automatic generation module through recording the test operation executed by the user through the GUI,
the automatic generation module of the test case and the test script comprises a Selenium.
Optionally, as shown in the dashed box of fig. 2, the automated testing method according to the present invention further includes:
step S218: the method comprises the steps of using a test environment construction module to construct a Docker mirror image of software to be tested and/or web browser software based on a Docker virtualization technology, and further constructing a virtual test environment of the software to be tested, wherein the test environment construction module comprises Jenkins, and the web browser software comprises Chrome web browser software in a Chrome-header mode.
According to the technical scheme of the invention, the method has the following advantages:
1. the manual operation steps in the automatic testing process are reduced, the life cycle of software development is shortened, the workload of development and testing personnel is reduced, and the complexity of software product maintenance is reduced.
2. The automatic testing scheme from the (front) end to the (back) end is provided, the end-to-end testing script (comprising the testing case) can be automatically generated through recording the (back) end operation actually called by the front end, and professional testers do not need to write codes. And a clean test environment can be automatically deployed and a test script can be executed when the software code is submitted and updated, and finally a test report is generated and fed back to a developer.
3. The automatically generated scripts and containers can be reused, and the resource consumption and the maintenance complexity are reduced.
4. The applicability is strong, and different scripts can be automatically generated only by executing recording operation aiming at different languages and architectures.
5. The test flow and the feedback flow of the test result are fully automatic, the personnel investment is reduced to the maximum extent, and the working efficiency is improved.
The above-described aspects may be implemented individually or in various combinations, and such variations are within the scope of the present invention.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the components may be implemented as software executed by a processor, such as a digital signal processor or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
Finally, it should be noted that: the above examples are only for illustrating the technical solutions of the present invention, and are not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (10)
1. An automated test system, comprising:
the source code management module is used for carrying out version management on a source code of the software to be tested;
the testing environment constructing module is used for constructing a testing environment of the software to be tested based on the source code of the software to be tested;
the automatic generation module of the test case and the test script is used for automatically generating the test case and the test script based on the test operation executed by the user through the GUI;
and the test module is used for automatically executing the test and generating a test report under the test environment based on the test case and the test script.
2. The automated test system of claim 1, further comprising:
and the software release module is used for automatically releasing the software which passes the automatic test.
3. The automated test system of claim 1, wherein the source code management module is further to:
the source code update message is automatically sent based on webhook,
the test environment construction module is further configured to:
receiving the source code updating message based on webhook, downloading and recompiling the updated source code, reconstructing the testing environment of the software to be tested,
wherein the source code management module comprises one of: SVN, Gitlab, the test environment construction module comprises Jenkins.
4. The automated test system of claim 1, wherein the test case and test script automatic generation module is further to:
automatically generating test cases and test scripts by recording test operations executed by a user through a GUI,
the automatic generation module of the test case and the test script comprises a Selenium.
5. The automated test system of claim 1, wherein the test environment construction module is further to:
constructing a Docker mirror image of the software to be tested and/or the web browser software based on a Docker virtualization technology, further constructing a virtual test environment of the software to be tested,
the test environment construction module comprises Jenkins, and the web browser software comprises Chrome web browser software in a Chrome-header mode.
6. An automated testing method, comprising:
using a source code management module to perform version management on a source code of software to be tested;
constructing a test environment of the software to be tested based on a source code of the software to be tested by using a test environment construction module;
automatically generating a test case and a test script based on a test operation executed by a user through a GUI (graphical user interface) by using a test case and test script automatic generation module;
and automatically executing the test and generating a test report under the test environment by using the test module based on the test case and the test script.
7. The automated testing method of claim 6, further comprising:
and automatically releasing the software passing the automatic test by using a software release module.
8. The automated testing method of claim 6, further comprising:
automatically sending source code update messages based on webhook by using the source code management module;
using the test environment construction module to receive the source code updating information based on webhook, downloading and recompiling the updated source code, reconstructing the test environment of the software to be tested,
wherein the source code management module comprises one of: SVN, Gitlab, the test environment construction module comprises Jenkins.
9. The automated testing method of claim 6, further comprising:
the test case and the test script are automatically generated by using the automatic generation module of the test case and the test script through recording the test operation executed by the user through the GUI,
the automatic generation module of the test case and the test script comprises a Selenium.
10. The automated testing method of claim 6, further comprising:
constructing a Docker image of the software to be tested and/or the web browser software based on a Docker virtualization technology by using the test environment constructing module so as to construct a virtual test environment of the software to be tested,
the test environment construction module comprises Jenkins, and the web browser software comprises Chrome web browser software in a Chrome-header mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811525198.XA CN111324522A (en) | 2018-12-13 | 2018-12-13 | Automatic test system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811525198.XA CN111324522A (en) | 2018-12-13 | 2018-12-13 | Automatic test system and method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111324522A true CN111324522A (en) | 2020-06-23 |
Family
ID=71166593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811525198.XA Pending CN111324522A (en) | 2018-12-13 | 2018-12-13 | Automatic test system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111324522A (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069057A (en) * | 2020-08-07 | 2020-12-11 | 长沙市到家悠享网络科技有限公司 | Code testing method, device, apparatus and storage medium |
| CN112231235A (en) * | 2020-12-10 | 2021-01-15 | 广东睿江云计算股份有限公司 | Test case compiling and testing method and system based on multi-party cooperation |
| CN112612702A (en) * | 2020-12-24 | 2021-04-06 | 光大兴陇信托有限责任公司 | Automatic testing method and device based on web |
| CN112732320A (en) * | 2021-01-14 | 2021-04-30 | 北京锐安科技有限公司 | Continuous integration method and device in software development process, electronic equipment and medium |
| CN112905456A (en) * | 2021-02-07 | 2021-06-04 | 重庆富民银行股份有限公司 | Automatic test report generation method based on MAVEN life cycle |
| CN113094261A (en) * | 2021-03-23 | 2021-07-09 | 杭州电魂网络科技股份有限公司 | Method, system, electronic device and storage medium for automatically updating test environment |
| CN113220570A (en) * | 2021-05-11 | 2021-08-06 | 青岛以萨数据技术有限公司 | Method and device for realizing online environment test based on defect library |
| CN113704136A (en) * | 2021-11-01 | 2021-11-26 | 深圳市明源云科技有限公司 | Test environment generation method, device, equipment and computer readable storage medium |
| CN115776456A (en) * | 2022-11-28 | 2023-03-10 | 重庆长安汽车股份有限公司 | Communication protocol testing method, device, testing equipment and storage medium |
| CN112612702B (en) * | 2020-12-24 | 2024-05-24 | 光大兴陇信托有限责任公司 | Automatic testing method and device based on web |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799515A (en) * | 2011-05-24 | 2012-11-28 | 腾讯科技（深圳）有限公司 | Application program testing method and device |
| CN104391690A (en) * | 2014-11-04 | 2015-03-04 | 中国石油天然气股份有限公司 | Application development system and method |
| CN106681926A (en) * | 2017-01-05 | 2017-05-17 | 网易（杭州）网络有限公司 | Method and device for testing webpage performances |
| CN106708740A (en) * | 2017-01-10 | 2017-05-24 | 网易（杭州）网络有限公司 | Script testing method and device |
| CN108921184A (en) * | 2018-04-18 | 2018-11-30 | 中国科学院信息工程研究所 | A kind of general type of webpage determination method |
-
2018
- 2018-12-13 CN CN201811525198.XA patent/CN111324522A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799515A (en) * | 2011-05-24 | 2012-11-28 | 腾讯科技（深圳）有限公司 | Application program testing method and device |
| CN104391690A (en) * | 2014-11-04 | 2015-03-04 | 中国石油天然气股份有限公司 | Application development system and method |
| CN106681926A (en) * | 2017-01-05 | 2017-05-17 | 网易（杭州）网络有限公司 | Method and device for testing webpage performances |
| CN106708740A (en) * | 2017-01-10 | 2017-05-24 | 网易（杭州）网络有限公司 | Script testing method and device |
| CN108921184A (en) * | 2018-04-18 | 2018-11-30 | 中国科学院信息工程研究所 | A kind of general type of webpage determination method |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112069057A (en) * | 2020-08-07 | 2020-12-11 | 长沙市到家悠享网络科技有限公司 | Code testing method, device, apparatus and storage medium |
| CN112231235A (en) * | 2020-12-10 | 2021-01-15 | 广东睿江云计算股份有限公司 | Test case compiling and testing method and system based on multi-party cooperation |
| CN112231235B (en) * | 2020-12-10 | 2021-03-30 | 广东睿江云计算股份有限公司 | Test case compiling and testing method and system based on multi-party cooperation |
| CN112612702A (en) * | 2020-12-24 | 2021-04-06 | 光大兴陇信托有限责任公司 | Automatic testing method and device based on web |
| CN112612702B (en) * | 2020-12-24 | 2024-05-24 | 光大兴陇信托有限责任公司 | Automatic testing method and device based on web |
| CN112732320A (en) * | 2021-01-14 | 2021-04-30 | 北京锐安科技有限公司 | Continuous integration method and device in software development process, electronic equipment and medium |
| CN112732320B (en) * | 2021-01-14 | 2024-05-10 | 北京锐安科技有限公司 | Continuous integration method and device for software development process, electronic equipment and medium |
| CN112905456B (en) * | 2021-02-07 | 2023-06-06 | 重庆富民银行股份有限公司 | MAVEN life cycle-based automatic test report generation method |
| CN112905456A (en) * | 2021-02-07 | 2021-06-04 | 重庆富民银行股份有限公司 | Automatic test report generation method based on MAVEN life cycle |
| CN113094261A (en) * | 2021-03-23 | 2021-07-09 | 杭州电魂网络科技股份有限公司 | Method, system, electronic device and storage medium for automatically updating test environment |
| CN113220570B (en) * | 2021-05-11 | 2024-03-19 | 青岛以萨数据技术有限公司 | Method and device for realizing online environment test based on defect library |
| CN113220570A (en) * | 2021-05-11 | 2021-08-06 | 青岛以萨数据技术有限公司 | Method and device for realizing online environment test based on defect library |
| CN113704136B (en) * | 2021-11-01 | 2022-01-28 | 深圳市明源云科技有限公司 | Test environment generation method, device, equipment and computer readable storage medium |
| CN113704136A (en) * | 2021-11-01 | 2021-11-26 | 深圳市明源云科技有限公司 | Test environment generation method, device, equipment and computer readable storage medium |
| CN115776456A (en) * | 2022-11-28 | 2023-03-10 | 重庆长安汽车股份有限公司 | Communication protocol testing method, device, testing equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111324522A (en) | Automatic test system and method | |
| EP3769223B1 (en) | Unified test automation system | |
| CN110532189B (en) | Continuous integration system, method and device | |
| US9760343B2 (en) | Application builder based on metadata | |
| US11138097B2 (en) | Automated web testing framework for generating and maintaining test scripts | |
| CN108776643B (en) | Target code merging control method and system based on version control process | |
| KR20200115020A (en) | Hyperledger fabric network creation method, controller and storage medium | |
| CN108228190B (en) | Persistent integration and delivery methods, systems, devices, and computer-readable storage media | |
| EP2503449A2 (en) | Single development test environment | |
| EP3447635A1 (en) | Application architecture generation | |
| CN111651352B (en) | Warehouse code merging method and device | |
| EP4246332A1 (en) | System and method for serverless application testing | |
| US20190073292A1 (en) | State machine software tester | |
| CN110727575B (en) | Information processing method, system, device and storage medium | |
| CN112579099A (en) | Code deployment method and device, storage medium and electronic equipment | |
| CN112596784B (en) | Iterative version deployment method and device | |
| US20230393825A1 (en) | Automated software deployment techniques | |
| CN111796863A (en) | Cross-environment project version management method | |
| CN114265595B (en) | Cloud native application development and deployment system and method based on intelligent contracts | |
| US20230297496A1 (en) | System and method for serverless application testing | |
| US20220058018A1 (en) | Automatically generating continuous integration pipelines | |
| CN114489999A (en) | Method and device for processing pipeline task, processor and electronic equipment | |
| JP6677345B2 (en) | Development operation support system, development management server, operation management server, their methods and programs | |
| Deshpande et al. | Test Automation and Continuous Integration using Jenkins for Smart Card OS | |
| CN111352637B (en) | Method, device and equipment for deploying machine learning 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 |