CN111639036A - Continuous integration test development method and system based on AI test - Google Patents
Continuous integration test development method and system based on AI test Download PDFInfo
- Publication number
- CN111639036A CN111639036A CN202010515346.0A CN202010515346A CN111639036A CN 111639036 A CN111639036 A CN 111639036A CN 202010515346 A CN202010515346 A CN 202010515346A CN 111639036 A CN111639036 A CN 111639036A
- Authority
- CN
- China
- Prior art keywords
- test
- project
- mabl
- script
- development
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 101
- 238000011161 development Methods 0.000 title claims abstract description 46
- 238000000034 method Methods 0.000 title claims abstract description 21
- 230000010354 integration Effects 0.000 title claims abstract description 17
- 238000013515 script Methods 0.000 claims abstract description 25
- 238000007726 management method Methods 0.000 claims description 6
- 238000010801 machine learning Methods 0.000 claims description 5
- 230000002085 persistent effect Effects 0.000 claims description 5
- 238000013500 data storage Methods 0.000 claims description 4
- 238000004806 packaging method and process Methods 0.000 claims description 4
- 230000001960 triggered effect Effects 0.000 claims description 2
- 238000013522 software testing Methods 0.000 description 7
- 230000000694 effects Effects 0.000 description 2
- 229940060321 after-bug Drugs 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002035 prolonged 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
-
- 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/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
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)
- Stored Programmes (AREA)
Abstract
The invention discloses a continuous integration test development method and a system based on AI test, the method comprises the following steps: s1, submitting a code to a remote warehouse; s2, triggering a script running code; s3, triggering a script to execute the MABL; s4, MABL executes AI test; s5, pushing a test result to a developer; and S6, storing the file into a local archive. The invention also provides a continuous integration test development system based on the AI test. By using the CI/CD environment and integrating the existing AI test product MABL, the invention can carry out the project code test in the project development stage, finds the problem in the development stage, modifies the problem in time, indirectly shortens the development period of the project, lightens the pressure of the test team and reduces the manual test cost of the company.
Description
Technical Field
The invention relates to the field of computers, in particular to a continuous integration test development method and system based on AI test.
Background
Software testing describes a process used to facilitate the identification of the correctness, integrity, security, and quality of software. In other words, software testing is a process of auditing or comparing between actual output and expected output. The classical definition of software testing is: the process of operating a program under specified conditions to discover program errors, to measure software quality, and to evaluate whether it meets design requirements.
Software testing industry standards (IEEE/ANSI) have been established, and the definition given under software testing in the software engineering terminology proposed by IEEE in 1983 is: "a process for running or testing a software system using manual or automatic means, with the purpose of checking whether it meets specified requirements or to figure out differences between expected and actual results". This definition explicitly states that the purpose of software testing is to verify that a software system meets requirements. It is not disposable any more, and is only the activity of development later stage, but fuses with the whole development flow. Software testing has become a specialty, requiring the use of specialized methods and tools, specialized talents and experts to undertake.
At present, an AI test-based tool is used for testing a project by a testing team after the project is finished, and pushing problems to developers after BUG is found, so that countless versions of the final project appear through one iteration of the form, the project development cycle time is indirectly prolonged, and the project development cost is increased.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provide a continuous integration test development method and system based on AI test, which provides a code test for project developers in the project development stage, solves the problem of BUG in the development process, shortens the development cycle of the project and reduces the software test cost of the project.
The purpose of the invention is realized by the following technical scheme:
a continuous integration test development method based on AI test comprises the following steps:
s1, submitting the code to a remote warehouse;
s2, triggering script running codes;
s3, triggering the script to execute the MABL;
s4, MABL performs AI testing;
s5, directly pushing the test result to a developer;
and S6, storing the data into a local archive.
Optionally, the submitting the code to the remote repository in step S1 includes the following sub-steps:
s101, building a CI/CD environment and developing projects based on the built environment;
s102, using Jenkins as a core management tool to complete continuous integration/continuous deployment of project tests;
s103, for different development voices, when codes are submitted, different scripts are triggered through Jenkins, development project classifications are packaged, and the development projects are submitted and issued to a remote warehouse.
Alternatively, in step S2, the script code must be executed based on the CI/CD environment, and the item execution address is acquired.
Optionally, in step S3, after the script code is successfully executed, executing script operation MABL, where the main steps are as follows:
s301, handing the MABL to Jenkins for management: configuring a MALL startup SHELL script into a build item in Jenkins, and triggering to run at regular time;
s302, writing a script program for running the MABL;
s303, directly triggering the written script program after the step S302 is finished;
s304, starting the MABL.
Optionally, in the step S4, the AI test executed by the MABL is to start testing the operated item after the MABL is successfully operated, and the main steps are as follows:
s401, writing the operation address of the item in the step S2 into a script;
s402, the MABL acquires the item operation address in the script;
and S403, reading the specified file in the disk by the MABL according to the configuration, acquiring the address of the item to be tested, and executing the AI intelligent test through automatic retrieval of the MABL.
A continuous integrated test development system based on AI test comprises
The project development module is used for developing projects based on the CI/CD environment by developers;
the code submitting module is used for acquiring project codes by a user, classifying, packaging and submitting the project codes to a test platform;
the project testing platform is used for a developer to locally test and run a project application program and generate a corresponding test report;
the test result pushing module is used for directly pushing the test report to the project developer after the project test is finished;
and the data storage module is used for storing the project test results into a local archive for machine learning.
The invention has the beneficial effects that: the scheme integrates the existing AI test technology into a CI/CD environment, tests the project in the development phase, finds the project problem, solves some BUG problems in the development phase, reduces the pressure of a test team, and indirectly shortens the project development period.
Drawings
FIG. 1 is a flow chart of the method of the present invention.
Fig. 2 is a schematic diagram of the system architecture of the present invention.
Detailed Description
In order to more clearly understand the technical features, objects, and effects of the present invention, embodiments of the present invention will now be described with reference to the accompanying drawings.
In this embodiment, as shown in fig. 1, a method for developing a persistent integration test based on an AI test includes the following steps:
step 1: the method comprises the steps of building a CI/CD environment, finishing continuous integration/continuous deployment of project testing by using Jenkins as a core management tool based on building environment development projects, triggering different scripts through the Jenkins when submitting codes according to different development voices, packaging classification of the development projects, and submitting and releasing the development projects to a remote warehouse.
Step 2: and triggering the script running code and acquiring the item running address based on the CI/CD environment.
And step 3: and (4) handing the MABL in Jenkins management, configuring the MABL starting SHELL script into a build item in Jenkins, and triggering to run at regular time. And then writing a script program for running the MABL, and directly triggering the written script program to run and start the MABL after the writing of the MABL script program is finished.
And 4, step 4: and after the MABL is successfully operated, starting to test the operated items, writing the operation address of the item in the step 2 into the script, and acquiring the item operation address in the script by the MABL. And the MABL reads the specified file in the disk according to the configuration, acquires the address of the item to be tested, executes AI intelligent test through automatic MABL retrieval, and outputs a test result report of the item software.
And 5, directly pushing a test result report to developers after the MABL test is finished.
And 6, storing the test result into a local archive for machine learning.
In this embodiment, as shown in fig. 2, a continuous integrated test development system based on an AI test is further provided, and includes a project development module, a code submission module, a project test platform, a test including push module, and a data storage module. The project development module is used for developing projects based on a CI/CD environment by developers; the code submitting module is used for acquiring project codes, classifying, packaging and submitting the project codes to a test platform; the project testing platform is used for a developer to locally test and run a project application program and generate a corresponding test report; the test report pushing module is used for directly pushing the test report to a project developer after the project test is finished; and the data storage module is used for storing the project test results into a local archive for machine learning.
In this embodiment, an operation flow of the continuous integrated test development system based on the AI test includes: developers build a CI/CD environment in the system and develop projects in a project development module. After the project development is completed, the project development codes are submitted to a project testing platform through a code submitting module. In the project testing platform, a developer locally tests project codes, a BUG problem possibly exists in the tested project codes, and the platform outputs a testing report after the testing is finished. The system directly pushes the test report to developers who submit project tests, and stores the test report in a local archive, so that subsequent machine learning is facilitated.
The foregoing shows and describes the general principles and broad features of the present invention and advantages thereof. It will be understood by those skilled in the art that the present invention is not limited to the embodiments described above, which are described in the specification and illustrated only to illustrate the principle of the present invention, but that various changes and modifications may be made therein without departing from the spirit and scope of the present invention, which fall within the scope of the invention as claimed. The scope of the invention is defined by the appended claims and equivalents thereof.
Claims (6)
1. A continuous integration test development method based on AI test is characterized by comprising the following steps: s1, submitting the code to a remote warehouse;
s2, triggering script running codes;
s3, triggering the script to execute the MABL;
s4, MABL performs AI testing;
s5, directly pushing the test result to a developer;
and S6, storing the data into a local archive.
2. The AI-test-based persistent integration test development method according to claim 1, wherein the step of submitting code to a remote repository in step S1 comprises the sub-steps of:
s101, building a CI/CD environment and developing projects based on the built environment;
s102, using Jenkins as a core management tool to complete continuous integration/continuous deployment of project tests;
s103, for different development voices, when codes are submitted, different scripts are triggered through Jenkins, development project classifications are packaged, and the development projects are submitted and issued to a remote warehouse.
3. The AI-test-based persistent integration test development method according to claim 1, wherein the script code must be executed based on CI/CD environment in step S2 while the item execution address is obtained.
4. The AI-test-based persistent integration test development method according to claim 1, wherein the step S3 is to execute script operation MABL after the script code is successfully executed, and the main steps are as follows:
s301, handing the MABL to Jenkins for management: configuring a MALL startup SHELL script into a build item in Jenkins, and triggering to run at regular time;
s302, writing a script program for running the MABL;
s303, directly triggering the written script program after the step S302 is finished;
s304, starting the MABL.
5. The AI-test-based persistent integration test development method according to claim 1, wherein the AI test executed by the MABL in the step S4 is to start testing the running project after the MABL is successfully run, and the main steps are as follows:
s401, writing the operation address of the item in the step S2 into a script;
s402, the MABL acquires the item operation address in the script;
and S403, reading the specified file in the disk by the MABL according to the configuration, acquiring the address of the item to be tested, and executing the AI intelligent test through automatic retrieval of the MABL.
6. A continuous integration test development system based on AI test is characterized by comprising
The project development module is used for developing projects based on the CI/CD environment by developers;
the code submitting module is used for acquiring project codes by a user, classifying, packaging and submitting the project codes to a test platform;
the project testing platform is used for a developer to locally test and run a project application program and generate a corresponding test report;
the test result pushing module is used for directly pushing the test report to the project developer after the project test is finished;
and the data storage module is used for storing the project test results into a local archive for machine learning.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010515346.0A CN111639036A (en) | 2020-06-08 | 2020-06-08 | Continuous integration test development method and system based on AI test |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202010515346.0A CN111639036A (en) | 2020-06-08 | 2020-06-08 | Continuous integration test development method and system based on AI test |
Publications (1)
Publication Number | Publication Date |
---|---|
CN111639036A true CN111639036A (en) | 2020-09-08 |
Family
ID=72330385
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202010515346.0A Pending CN111639036A (en) | 2020-06-08 | 2020-06-08 | Continuous integration test development method and system based on AI test |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN111639036A (en) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104375937A (en) * | 2014-11-19 | 2015-02-25 | 福建亿榕信息技术有限公司 | Continuous integration method and system of automated testing results |
WO2016177124A1 (en) * | 2015-07-29 | 2016-11-10 | 中兴通讯股份有限公司 | Method and device for implementing continuous integration test |
US20190068612A1 (en) * | 2017-08-30 | 2019-02-28 | Red Hat, Inc. | Setting application permissions in a cloud computing environment |
CN109408106A (en) * | 2018-09-27 | 2019-03-01 | 华东计算技术研究所(中国电子科技集团公司第三十二研究所) | Agile software development continuous integration method and system |
CN109426602A (en) * | 2017-07-18 | 2019-03-05 | 中国移动通信集团公司 | Detection method and equipment used in a kind of application development process |
CN110941556A (en) * | 2019-11-27 | 2020-03-31 | 厦门市美亚柏科信息股份有限公司 | Method for rapidly compiling test cases on Android platform |
-
2020
- 2020-06-08 CN CN202010515346.0A patent/CN111639036A/en active Pending
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104375937A (en) * | 2014-11-19 | 2015-02-25 | 福建亿榕信息技术有限公司 | Continuous integration method and system of automated testing results |
WO2016177124A1 (en) * | 2015-07-29 | 2016-11-10 | 中兴通讯股份有限公司 | Method and device for implementing continuous integration test |
CN109426602A (en) * | 2017-07-18 | 2019-03-05 | 中国移动通信集团公司 | Detection method and equipment used in a kind of application development process |
US20190068612A1 (en) * | 2017-08-30 | 2019-02-28 | Red Hat, Inc. | Setting application permissions in a cloud computing environment |
CN109408106A (en) * | 2018-09-27 | 2019-03-01 | 华东计算技术研究所(中国电子科技集团公司第三十二研究所) | Agile software development continuous integration method and system |
CN110941556A (en) * | 2019-11-27 | 2020-03-31 | 厦门市美亚柏科信息股份有限公司 | Method for rapidly compiling test cases on Android platform |
Non-Patent Citations (1)
Title |
---|
马睿: "自动化测试解决方案研究" * |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11281570B2 (en) | Software testing method, system, apparatus, device medium, and computer program product | |
CN108509336B (en) | Operating system standard formalization verification and test method | |
AU2005203492B2 (en) | Automated test case verification that is loosely coupled with respect to automated test case execution | |
US8522214B2 (en) | Keyword based software testing system and method | |
US7895575B2 (en) | Apparatus and method for generating test driver | |
CN111679868A (en) | Automobile software model integration method, device, equipment and storage medium | |
US9342439B2 (en) | Command coverage analyzer | |
CN113868120A (en) | Industrial software debugging method and device, computer equipment and storage medium | |
CN103186463B (en) | Determine the method and system of the test specification of software | |
US20110041116A1 (en) | Formal analysis driven based evolution of requirements specifications | |
CN114237754B (en) | Data loading method and device, electronic equipment and storage medium | |
CN113804451A (en) | Automatic simulation test method and device for intelligent driving of automobile | |
Thooriqoh et al. | Selenium Framework for Web Automation Testing: A Systematic Literature Review | |
CN111639036A (en) | Continuous integration test development method and system based on AI test | |
Saavedra et al. | GitBug-Actions: Building Reproducible Bug-Fix Benchmarks with GitHub Actions | |
CN111506513B (en) | File system testing method based on hierarchical model | |
US7231619B1 (en) | Extended model checking hardware verification | |
TWI676942B (en) | A method and system implemented in billing domain by accelerating batch execution | |
Biondi et al. | Papyrus-based safety analysis automatization | |
Kovalev et al. | On the problem of predicting meantime between failures on the basis of data from automated testing of on-board software components | |
CN109669868A (en) | The method and system of software test | |
CN116594918B (en) | Test case change influence analysis method, device, equipment and storage medium | |
Huang et al. | Testing for dynamic software update: An object-state-oriented approach | |
CN116932414B (en) | Method and equipment for generating interface test case and computer readable storage medium | |
CN114253780A (en) | Hard disk performance test method and system based on AMD processor |
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 |
Application publication date: 20200908 |
|
RJ01 | Rejection of invention patent application after publication |