CN113836039A - Automatic smoking test method and system - Google Patents
Automatic smoking test method and system Download PDFInfo
- Publication number
- CN113836039A CN113836039A CN202111238811.1A CN202111238811A CN113836039A CN 113836039 A CN113836039 A CN 113836039A CN 202111238811 A CN202111238811 A CN 202111238811A CN 113836039 A CN113836039 A CN 113836039A
- Authority
- CN
- China
- Prior art keywords
- version
- test
- smoking
- task
- server
- 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
- 230000000391 smoking effect Effects 0.000 title claims abstract description 151
- 238000010998 test method Methods 0.000 title claims abstract description 11
- 238000012360 testing method Methods 0.000 claims abstract description 261
- 238000012544 monitoring process Methods 0.000 claims abstract description 32
- 238000009434 installation Methods 0.000 claims abstract description 15
- 239000000779 smoke Substances 0.000 claims description 18
- 238000000034 method Methods 0.000 claims description 17
- 230000001960 triggered effect Effects 0.000 claims description 9
- 238000012384 transportation and delivery Methods 0.000 abstract 2
- 230000010354 integration Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 5
- 238000010276 construction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000007547 defect Effects 0.000 description 1
- 230000002950 deficient Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/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 provides an automatic smoking test method and system, comprising the following steps: predetermining a smoking test case, compiling a corresponding smoking test script according to the smoking test case, and configuring a smoking test task and a monitoring version updating task in a Jenkins system of a test server; when the version server receives an update code submitted by a developer aiming at a preset project, the update code is sent to the compiling server; the compiling server constructs a version deliverable according to the updating code, updates the version library and uploads the version deliverable to a storage address; and when the version database is monitored to be updated by the monitoring version updating task on the test server, triggering the smoking test task to enable the smoking test task to download the version deliveries from the storage address, so that the mobile terminal connected with the test server installs the version deliveries, executing the project smoking test script after the installation is finished, and generating a test report after the execution is finished. The invention can improve the efficiency of smoking test.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of smoking test technologies, and in particular, to an automated smoking test method and system.
Background
In the software development test, in order to verify whether a newly compiled software version has a fatal defect, whether a main business process can normally run or not is not influenced, the normal operation of the next round of test is not influenced, and a manual smoking test is performed before the test is formally started. With the continuous expansion of company services, the variety of software products is continuously expanded, the number of mobile application items is increased, the testing efficiency of manual smoking tests is low, and the testing requirements are not met.
Disclosure of Invention
One or more embodiments of the present specification describe an automated smoke test method and system.
According to a first aspect, there is provided an automated smoking test method comprising:
predetermining a smoking test case, compiling a corresponding smoking test script according to the smoking test case, and configuring a smoking test task and a monitoring version updating task in a Jenkins system of a test server;
when the version server receives an update code submitted by a developer aiming at a preset project, the update code is sent to a compiling server;
the compiling server constructs a version deliverable according to the updating code, updates the version library and uploads the version deliverable to a corresponding storage address;
and when the version database is monitored to be updated by the monitoring version updating task on the test server, triggering the smoking test task to enable the smoking test task to download the version deliverable from the storage address, enabling a mobile terminal connected with the test server to install the version deliverable, executing the smoking test script corresponding to the project after the installation is finished, and generating a test report after the execution is finished.
According to a second aspect, there is provided an automated smoking test system comprising:
the testing server is used for acquiring a corresponding smoking testing script compiled by a worker according to a predetermined smoking testing case, and configuring a smoking testing task and a monitoring version updating task in a Jenkins system;
the version server is used for sending the update codes to the compiling server when receiving the update codes submitted by developers aiming at the preset project;
the compiling server is used for constructing a version deliverable according to the updating code, updating the version library and uploading the version deliverable to a corresponding storage address;
the test server is further configured to trigger the smoking test task when the version base update is monitored by the monitoring version update task, so that the smoking test task downloads the version deliverable from the storage address, so that the mobile terminal connected to the test server installs the version deliverable, executes the smoking test script corresponding to the project after installation is completed, and generates a test report after execution is completed.
According to the automatic smoking test method provided by the embodiment of the specification, a Jenkins system is built on a test server, and then a smoking test task and a monitoring version updating task are configured on the Jenkins system. And determining a smoking test case, and further compiling a smoking test script. This completes the preparation. After the developer submits the update code, the worker pulls the update code on the version server to the compiling service to construct a version deliverable, updates the version number in the version library, and uploads the version deliverable to a corresponding storage position. And when the monitoring version updating task detects the updating of the version library, triggering the smoking test task to perform smoking test, and after the execution is finished, generating a test report by the smoking test task. In the test process, personnel participate a little, can realize the automation of smoking test basically, compared with the manual smoking test in the prior art, the efficiency of smoking test is greatly improved, the time cost is saved, and the smoking test script can be reused without rewriting the script every time.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present specification, and other drawings can be obtained by those skilled in the art without creative efforts.
FIG. 1 is a schematic flow diagram of an automated smoke test method in one embodiment of the present description;
FIG. 2 is a schematic flow chart diagram of an automated smoke test method in one embodiment of the present description;
figure 3 is a partial flow diagram of a method for automated smoke testing in one embodiment of the present description.
Detailed Description
The scheme provided by the specification is described below with reference to the accompanying drawings.
In a first aspect, the present invention provides an automated smoke test method, as shown in fig. 1 and 2, comprising the steps of:
s110, predetermining a smoking test case, compiling a corresponding smoking test script according to the smoking test case, and configuring a smoking test task and a monitoring version updating task in a Jenkins system of a test server;
it is understood that the smoking test refers to a strategy for quickly verifying the basic function of the software version package in the software development process, and is a means for confirming and verifying the basic function of the software. The main purpose of performing a smoke test is to quickly verify whether the basic functions of the software are defective. If the test case of the smoking test fails, no further testing is necessary.
In specific implementation, an automatic smoking test case can be designed to serve as a basis for compiling a smoking test script. But some cases can be directly selected from the existing test cases to be used as smoking test cases. That is, the predetermined smoking test case may include: and selecting a test case with the first grade from all test cases aiming at the preset project as the smoking test case.
It can be understood that there are many use cases during testing, and the use cases have different levels, for example, Level1, Level2, Level3, Level4, etc., Level1 is a Level-one test case, and represents a use case for testing a main core function, and the smoking test mainly aims at the core basic function of a project, so that the use case of Level1 is selected as the smoking test case.
It can be understood that after the smoking test case is determined, a corresponding smoking test script can be written according to the smoking test case, for example, the smoking test script is written according to an operating system of the mobile terminal by using an Airtest tool. The Airtest tool is a cross-platform UI automatic test framework and is suitable for script writing of App. Operating systems, e.g., Android system, IOS. Here, it is necessary to write a corresponding smoking test script for each operating system, so that the smoking test can be completed together with mobile terminals of different operating systems.
It can be understood that after the smoking test script is written, the task can be configured in the Jenkins system. The Jenkins system is a continuous integration tool developed based on Java, is used for monitoring continuous and repeated work, and aims to provide an open and easy-to-use software platform so that software projects can be continuously integrated. Multiple tasks, such as the above-described smoke test task, the listening version update task, and the like, may be established and deployed in the Jenkins system.
It is understood that the configuration task refers to a process of configuring a jobs in the Jenkins system, trigger conditions of the configuration task, a storage path of an execution script required for configuration, which operating system corresponds to which script and version number are configured, and other various information.
S120, when the version server receives an update code submitted by a developer aiming at a preset project, the update code is sent to a compiling server;
it will be appreciated that after a developer writes update code for a project, it is submitted to the version server. The worker will pull the latest code from the version server to the compilation server.
S130, the compiling server constructs a version deliverable according to the updating code, updates the version library and uploads the version deliverable to a corresponding storage address;
in a specific implementation, S130 may include: and the compiling server constructs version deliverables corresponding to a plurality of operating system types according to the updating codes, updates the version library, generates corresponding storage addresses according to the name, the version number and each operating system type of a preset project, and uploads the version deliverables corresponding to each operating system type to the corresponding storage addresses.
It can be understood that the compiling server constructs the update code to obtain a version deliverable, the version deliverable for the Android system is an APK package, the version deliverable for the IOS system is an IPA package, and the version library on the compiling server is updated, for example, the version number of the latest version in the version library is updated. And then different storage addresses are built for the version deliverables of different operating systems, and the version deliverables are uploaded to the corresponding storage addresses.
The construction method of the storage address can be as follows: and generating corresponding storage addresses according to the names, version numbers and each operating system type of the preset projects, namely, storing corresponding version deliverables of different projects, different versions and different operating systems in different positions.
And S140, when the version library is monitored to be updated by the monitoring version updating task on the test server, triggering the smoking test task to enable the smoking test task to download the version deliverable from the storage address, so that the mobile terminal connected with the test server installs the version deliverable, executes the smoking test script corresponding to the project after the installation is finished, and generates a test report after the execution is finished.
It can be understood that the version library on the compiling server is queried by the monitoring version update task on the testing server at intervals (for example, 5 minutes), so that after the version library is updated, the monitoring version update task on the testing server also queries that the version library is updated, a smoking test task is triggered at this time, and after the smoking test task is triggered, a version consignment is downloaded from a corresponding storage address, so that the downloaded version consignment is installed on the mobile terminal, and then a corresponding smoking test script is executed, so that a smoking test is performed, and after the test is completed, a test report is generated by the smoking test task.
In a specific implementation, the downloading, by the smoking test task, the version deliverable from the storage address to enable the mobile terminal connected to the test server to install the version deliverable, and executing the smoking test script corresponding to the project after the installation is completed may include: and the smoke test task assembles a corresponding storage address according to the operating system type of the mobile terminal connected with the test server, the version number acquired from the version library and the name of a preset project, downloads a corresponding version deliverable according to the storage address so as to enable the mobile terminal to install the version deliverable, executes the smoke test script corresponding to the operating system type of the mobile terminal and the name of the preset project after the installation is finished, and generates a test report after the execution is finished.
For example, the mobile terminal connected to the test server is an IOS system, the smoking test task determines a storage address of the corresponding version deliverable according to the IOS system, the latest version number obtained from the version library, and the name a of the item, the storage address is determined in the same manner as the storage address formed on the compiling server for storing the constructed version deliverable, and the test server determines the storage address so as to be able to download the corresponding version deliverable from the storage address. When the smoking test task of the test server mountain assembles the storage address, the corresponding version deliverable can be downloaded from the storage address. And then installing the downloaded version deliverable on the mobile terminal, and executing the smoking test script corresponding to the IOS system and the project name A after the version deliverable is installed on the mobile terminal, thereby starting the smoking test.
In specific implementation, when the monitoring version update task on the test server monitors the version library update, triggering the smoking test task may include: when the monitoring version updating task on the test server monitors that the version library has a newly added version number and the version number is in a successful state, triggering the smoking test task; and when the version library has a newly added version number and the version number is in a failure state or the version library does not have the newly added version number, the smoking test task is not triggered.
That is, referring to fig. 3, only if the version library on the compiling server has a new version number and the version number is in a success state, the smoking test task is triggered. The version number is a success status, indicating that the construction of the version deliverable was successful. If the version number is in a failure state, the construction of the version deliverable is failed. Therefore, if the version library has no newly added version number or even if the version library has the newly added version number but the version number is in a failure state, the smoking test task cannot be triggered.
In specific implementation, after the test is completed, the smoking test task on the test server can also be used for informing the test report to a developer through an email, so that the developer can know whether the update code meets the basic core function requirement.
For example, the flow of the smoke test may generally include the following steps:
step 1: building a test Jenkins continuous integration platform;
step 2: determining an automatic smoking test case as a basis for compiling an automatic smoking test script;
and step 3: compiling an automatic smoking test script of the project;
and 4, step 4: configuring a smoking test task in a test Jenkins continuous integration platform;
and 5: configuring a monitoring version updating task in a test Jenkins continuous integration platform;
step 6: and the version monitoring and updating task monitors that the version base has an updated version number and is in a successful state, and triggers a smoking test task so as to execute: assembling a storage address (for example, a fixed address, a project name, an operating system type of the mobile terminal and a version number), downloading a corresponding version deliverable according to the storage address, installing the version deliverable on the mobile terminal, and executing a corresponding smoking test script according to an operating system and the project name of the mobile terminal;
and 7: and automatically generating a test report after the script is operated, and automatically sending a mail to a relevant member of the project.
Step 1, a Jenkins testing continuous integration platform is set up and used for configuring Jenkins tasks, monitoring the outside and calling the executed work.
In the step 2, in the determination of the automatic smoking test case, the tester selects a case of Level1 as a smoking test case in the test case according to the test requirements and the core flow of the project.
And 3, in the smoking test script for the writing project, according to the smoking test case, the Airtest tool can be used for testing the smoking test script corresponding to the Android and the IOS.
And 4, when the smoking test task is configured in the test Jenkins continuous integration platform, the smoking test task can be configured in the test Jenkins continuous integration platform according to the actual requirements of the project. When the triggering condition of the task is reached (namely the monitoring version updating task monitors that the version base has the updated version number and is in a success state), the execution of the task is automatically triggered. The naming of the smoking test task may be project name + operating system type of the mobile terminal (i.e., Android or IOS).
And 5, when the Jenkins continuous integration platform configuration monitoring version updating task is tested, the monitoring version updating task can be set to be in a state of inquiring the version library once every five minutes.
And 6, when the version database is monitored to have the update of the version number and is in a successful state, triggering the execution of the smoking test task.
It can be understood that before executing the smoking test script, the test server where the Jenkins continuous integration platform is located needs to be tested to be connected with the mobile terminal.
The invention relates to an automatic smoking test scheme based on mobile application. And determining a smoking test case, and further compiling a smoking test script. This completes the preparation. After the developer submits the update code, the worker pulls the update code on the version server to the compiling service to construct a version deliverable, updates the version number in the version library, and uploads the version deliverable to a corresponding storage position. And when the monitoring version updating task detects that the version base is updated and the latest version number is in a successful state, triggering a smoking test task, assembling a storage address according to information such as an operating system, a project name, a version number and the like of the mobile terminal connected with the test server, and further downloading a corresponding version deliverable, thereby installing the version deliverable on the mobile terminal. And then executing the corresponding smoking test script according to the operating system and the project name to perform smoking test, and after the execution is finished, generating a test report by the smoking test task and sending the test report to a developer to finish the smoking test. In the test process, personnel participate a little, can realize the automation of smoking test basically, compared with the manual smoking test in the prior art, the efficiency of smoking test is greatly improved, the time cost is saved, and the smoking test script can be reused without rewriting the script every time.
In a second aspect, the present invention provides an automated smoking test system, comprising:
the testing server is used for acquiring a corresponding smoking testing script compiled by a worker according to a predetermined smoking testing case, and configuring a smoking testing task and a monitoring version updating task in a Jenkins system;
the version server is used for sending the update codes to the compiling server when receiving the update codes submitted by developers aiming at the preset project;
the compiling server is used for constructing a version deliverable according to the updating code, updating the version library and uploading the version deliverable to a corresponding storage address;
the test server is further configured to trigger the smoking test task when the version base update is monitored by the monitoring version update task, so that the smoking test task downloads the version deliverable from the storage address, so that the mobile terminal connected to the test server installs the version deliverable, executes the smoking test script corresponding to the project after installation is completed, and generates a test report after execution is completed.
In some embodiments, the building, by the compiling server, a version deliverable according to the update code, updating the version library, and uploading the version deliverable to a corresponding storage address specifically includes: the compiling server constructs version deliverables corresponding to a plurality of operating system types according to the updating codes, updates the version library, generates corresponding storage addresses according to the name, the version number and each operating system type of a preset project, and uploads the version deliverables corresponding to each operating system type to the corresponding storage addresses;
correspondingly, the smoking test task in the test server downloads the version deliverable from the storage address so that the mobile terminal connected with the test server installs the version deliverable, and executes the smoking test script corresponding to the project after the installation is completed, and the method comprises the following steps: and the smoke test task assembles a corresponding storage address according to the operating system type of the mobile terminal connected with the test server, the version number acquired from the version library and the name of a preset project, downloads a corresponding version deliverable according to the storage address so as to enable the mobile terminal to install the version deliverable, executes the smoke test script corresponding to the operating system type of the mobile terminal and the name of the preset project after the installation is finished, and generates a test report after the execution is finished.
In some embodiments, the test server is further configured to mail the test report to a developer through the smoking test task.
In some embodiments, the triggering the smoking test task when the version library update is monitored by the monitoring version update task in the test server includes:
when the monitoring version updating task on the test server monitors that the version library has a newly added version number and the version number is in a successful state, triggering the smoking test task; and when the version library has a newly added version number and the version number is in a failure state or the version library does not have the newly added version number, the smoking test task is not triggered.
In some embodiments, the predetermined smoking test case is a test case with a first class selected from among test cases for a preset item.
It is to be understood that the system provided by the present invention corresponds to the method provided by the first aspect, and the explanation, the examples, the detailed description, the advantages, and the like of the related contents can be referred to the corresponding parts in the first aspect.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this disclosure may be implemented in hardware, software, hardware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.
The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.
Claims (10)
1. An automated smoking test method, comprising:
predetermining a smoking test case, compiling a corresponding smoking test script according to the smoking test case, and configuring a smoking test task and a monitoring version updating task in a Jenkins system of a test server;
when the version server receives an update code submitted by a developer aiming at a preset project, the update code is sent to a compiling server;
the compiling server constructs a version deliverable according to the updating code, updates the version library and uploads the version deliverable to a corresponding storage address;
and when the version database is monitored to be updated by the monitoring version updating task on the test server, triggering the smoking test task to enable the smoking test task to download the version deliverable from the storage address, enabling a mobile terminal connected with the test server to install the version deliverable, executing the smoking test script corresponding to the project after the installation is finished, and generating a test report after the execution is finished.
2. The method of claim 1,
the compiling server constructs a version deliverable according to the updating code, updates the version library and uploads the version deliverable to a corresponding storage address, and the method comprises the following steps: the compiling server constructs version deliverables corresponding to a plurality of operating system types according to the updating codes, updates the version library, generates corresponding storage addresses according to the name, the version number and each operating system type of a preset project, and uploads the version deliverables corresponding to each operating system type to the corresponding storage addresses;
correspondingly, the smoking test task downloads the version deliverable from the storage address so as to enable a mobile terminal connected with the test server to install the version deliverable, and executes a smoking test script corresponding to the project after the installation is completed, and the method comprises the following steps: and the smoke test task assembles a corresponding storage address according to the operating system type of the mobile terminal connected with the test server, the version number acquired from the version library and the name of a preset project, downloads a corresponding version deliverable according to the storage address so as to enable the mobile terminal to install the version deliverable, executes the smoke test script corresponding to the operating system type of the mobile terminal and the name of the preset project after the installation is finished, and generates a test report after the execution is finished.
3. The method of claim 1, wherein the smoke test task on the test server is further configured to mail the test report to a developer.
4. The method of claim 1, wherein triggering the smoking test task when the listening version update task on the test server listens for the version library update comprises:
when the monitoring version updating task on the test server monitors that the version library has a newly added version number and the version number is in a successful state, triggering the smoking test task; and when the version library has a newly added version number and the version number is in a failure state or the version library does not have the newly added version number, the smoking test task is not triggered.
5. The method of claim 1, wherein predetermining the smoking test case comprises: and selecting a test case with the first grade from all test cases aiming at the preset project as the smoking test case.
6. An automated smoking test system, comprising:
the testing server is used for acquiring a corresponding smoking testing script compiled by a worker according to a predetermined smoking testing case, and configuring a smoking testing task and a monitoring version updating task in a Jenkins system;
the version server is used for sending the update codes to the compiling server when receiving the update codes submitted by developers aiming at the preset project;
the compiling server is used for constructing a version deliverable according to the updating code, updating the version library and uploading the version deliverable to a corresponding storage address;
the test server is further configured to trigger the smoking test task when the version base update is monitored by the monitoring version update task, so that the smoking test task downloads the version deliverable from the storage address, so that the mobile terminal connected to the test server installs the version deliverable, executes the smoking test script corresponding to the project after installation is completed, and generates a test report after execution is completed.
7. The system of claim 6,
the building of a version deliverable according to the update code in the compiling server, updating the version library, and uploading the version deliverable to a corresponding storage address specifically comprises: the compiling server constructs version deliverables corresponding to a plurality of operating system types according to the updating codes, updates the version library, generates corresponding storage addresses according to the name, the version number and each operating system type of a preset project, and uploads the version deliverables corresponding to each operating system type to the corresponding storage addresses;
correspondingly, the smoking test task in the test server downloads the version deliverable from the storage address so that the mobile terminal connected with the test server installs the version deliverable, and executes the smoking test script corresponding to the project after the installation is completed, and the method comprises the following steps: and the smoke test task assembles a corresponding storage address according to the operating system type of the mobile terminal connected with the test server, the version number acquired from the version library and the name of a preset project, downloads a corresponding version deliverable according to the storage address so as to enable the mobile terminal to install the version deliverable, executes the smoke test script corresponding to the operating system type of the mobile terminal and the name of the preset project after the installation is finished, and generates a test report after the execution is finished.
8. The system of claim 6, wherein the test server is further configured to mail the test report to a developer via the smoke test task.
9. The system of claim 6, wherein the listening version update task in the test server triggers the smoking test task when it listens for the version library update, comprising:
when the monitoring version updating task on the test server monitors that the version library has a newly added version number and the version number is in a successful state, triggering the smoking test task; and when the version library has a newly added version number and the version number is in a failure state or the version library does not have the newly added version number, the smoking test task is not triggered.
10. The system of claim 6, wherein the predetermined smoking test case is a test case with a first selected level among test cases for a predetermined project.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111238811.1A CN113836039A (en) | 2021-10-25 | 2021-10-25 | Automatic smoking test method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111238811.1A CN113836039A (en) | 2021-10-25 | 2021-10-25 | Automatic smoking test method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113836039A true CN113836039A (en) | 2021-12-24 |
Family
ID=78965878
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111238811.1A Pending CN113836039A (en) | 2021-10-25 | 2021-10-25 | Automatic smoking test method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113836039A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579467A (en) * | 2022-03-18 | 2022-06-03 | 山东云海国创云计算装备产业创新中心有限公司 | Smoking test system and method based on release subscription mechanism |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130311982A1 (en) * | 2012-05-15 | 2013-11-21 | Oracle International Corporation | Automated upgrade for an operating system using a gateway server |
| CN105786691A (en) * | 2014-12-25 | 2016-07-20 | 重庆重邮信科通信技术有限公司 | Automatic integration testing device, method and system of mobile terminal |
| WO2019072110A1 (en) * | 2017-10-11 | 2019-04-18 | 阿里巴巴集团控股有限公司 | Method for generating application program, apparatus, system, device, and medium |
| CN111857801A (en) * | 2020-07-08 | 2020-10-30 | 广州云徙科技有限公司 | Construction method of mobile application |
| CN112130867A (en) * | 2020-08-05 | 2020-12-25 | 中国电子科技集团公司第二十八研究所 | Research, development and test integrated system |
| CN112269742A (en) * | 2020-10-29 | 2021-01-26 | 北京浪潮数据技术有限公司 | Jenkins-based automatic white box testing method and device and readable storage medium |
-
2021
- 2021-10-25 CN CN202111238811.1A patent/CN113836039A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130311982A1 (en) * | 2012-05-15 | 2013-11-21 | Oracle International Corporation | Automated upgrade for an operating system using a gateway server |
| CN105786691A (en) * | 2014-12-25 | 2016-07-20 | 重庆重邮信科通信技术有限公司 | Automatic integration testing device, method and system of mobile terminal |
| WO2019072110A1 (en) * | 2017-10-11 | 2019-04-18 | 阿里巴巴集团控股有限公司 | Method for generating application program, apparatus, system, device, and medium |
| CN111857801A (en) * | 2020-07-08 | 2020-10-30 | 广州云徙科技有限公司 | Construction method of mobile application |
| CN112130867A (en) * | 2020-08-05 | 2020-12-25 | 中国电子科技集团公司第二十八研究所 | Research, development and test integrated system |
| CN112269742A (en) * | 2020-10-29 | 2021-01-26 | 北京浪潮数据技术有限公司 | Jenkins-based automatic white box testing method and device and readable storage medium |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114579467A (en) * | 2022-03-18 | 2022-06-03 | 山东云海国创云计算装备产业创新中心有限公司 | Smoking test system and method based on release subscription mechanism |
| CN114579467B (en) * | 2022-03-18 | 2024-04-02 | 山东云海国创云计算装备产业创新中心有限公司 | Smoking testing system and method based on publish-subscribe mechanism |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10545469B2 (en) | Systems and methods for self provisioning building equipment | |
| CN110008123B (en) | Method for automatically deploying test software and corresponding device | |
| CN113703730A (en) | Continuous integration method and device, computer equipment and storage medium | |
| US20070038991A1 (en) | Method and apparatus for managing patchable software systems | |
| CN108228190B (en) | Persistent integration and delivery methods, systems, devices, and computer-readable storage media | |
| CN111258561A (en) | Method for starting and monitoring software automatic compiling and deploying | |
| CN111309636B (en) | Robot automation test system, method, construction server and storage medium | |
| CN112965913B (en) | Java software dependency conflict problem automatic repairing method | |
| CN106648762B (en) | Method and device for building development environment | |
| CN114880220B (en) | Development system and method of vehicle automatic driving software | |
| CN105389187B (en) | System updating method | |
| CN113836039A (en) | Automatic smoking test method and system | |
| CN113111000A (en) | Continuous integration automation test system and method, electronic device and storage medium | |
| CN110888652A (en) | Multi-version construction method based on jenkins plug-in and terminal | |
| CN113835742A (en) | Continuous integration method and software development system | |
| CN111309602A (en) | Software testing method, device and system | |
| CN108319551B (en) | Software testing method and device, computer equipment and readable storage medium | |
| CN113886220A (en) | Application upgrade test method and tool based on Linux operating system | |
| CN114281367A (en) | Big data platform deployment method and system for trust and creation environment | |
| CN111581081B (en) | Automatic test system and method | |
| CN114816449A (en) | Automatic deployment method and device | |
| CN106648797A (en) | Method and system for installing test software, test server and shared server | |
| CN113886008A (en) | Virtual machine management method, system, device and medium | |
| CN112015427A (en) | Method and device for building multiple compiling environments and electronic equipment | |
| CN114064508B (en) | Mobile terminal software testing method and system based on group control technology |
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: 20211224 |