CN110990261A - Test management system, method and platform - Google Patents
Test management system, method and platform Download PDFInfo
- Publication number
- CN110990261A CN110990261A CN201911088952.2A CN201911088952A CN110990261A CN 110990261 A CN110990261 A CN 110990261A CN 201911088952 A CN201911088952 A CN 201911088952A CN 110990261 A CN110990261 A CN 110990261A
- Authority
- CN
- China
- Prior art keywords
- test
- test plan
- execution
- plan
- script
- 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 305
- 238000000034 method Methods 0.000 title abstract description 10
- 238000013515 script Methods 0.000 claims abstract description 46
- 238000004806 packaging method and process Methods 0.000 claims abstract description 9
- 238000012795 verification Methods 0.000 claims description 34
- 238000007726 management method Methods 0.000 claims description 30
- 238000012986 modification Methods 0.000 claims description 10
- 230000004048 modification Effects 0.000 claims description 10
- 238000012856 packing Methods 0.000 claims description 10
- 230000001360 synchronised effect Effects 0.000 claims description 10
- 238000010586 diagram Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 2
- 239000000725 suspension Substances 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000010998 test method 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
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 embodiment of the invention discloses a test management system, a method and a platform, which comprises a test plan creating unit, a test management unit and a test management unit, wherein the test plan creating unit is used for making a test plan according to test requirements and storing the test plan into a database; the test plan verifying unit is used for verifying the test plan according to a verifying rule; the test environment deployment unit is used for compiling and packaging according to a project source code path in the test plan, triggering the test node to deploy the executive machine and carrying out FTP folder synchronization on the executive machine; the test script checking execution unit is used for distributing execution machines according to a task execution list in a test plan, creating a task list of each execution machine, analyzing a task execution rule, calling a project script, executing the task list in a multithreading concurrent mode and recording an execution result. The invention sequentially checks the test plan, deploys and checks the test environment and checks the test script, and executes the test after the checks are passed, thereby ensuring the smooth test, improving the test efficiency and ensuring the reliability of the test result.
Description
Technical Field
The invention relates to the technical field of server testing, in particular to a test management system, a method and a platform.
Background
The test management system is used as an important information management platform and provides management for test processes and test data, so that the automatic test efficiency is improved, and the test plan data is the premise of automatic test execution.
At present, a test management system manages a test plan in a table mode, and does not perform online unified management, so that management is disordered, and the test efficiency and the accuracy of a test result are seriously influenced.
Disclosure of Invention
The embodiment of the invention provides a test management system, a test management method and a test management platform, which are used for solving the problems in the prior art.
In order to solve the technical problem, the embodiment of the invention discloses the following technical scheme:
a first aspect of the present invention provides a test management system, including:
the test plan creating unit is used for making a test plan according to the test requirements and storing the test plan into a database, wherein the test plan comprises test basic information, a task execution list, execution case correlation information and a project script list;
the test plan verification unit is used for verifying the test plan according to the verification rule, and the verification object comprises the number of the executors, the configuration of the executors, test cases and test data;
the test environment deployment unit is used for compiling and packaging according to a project source code path in the test plan, triggering the test node to deploy the executive machine and carrying out FTP folder synchronization on the executive machine;
the test script checking execution unit is used for distributing execution machines according to a task execution list in a test plan, creating a task list of each execution machine, analyzing a task execution rule, calling a project script, executing the task list in a multithreading concurrent mode and recording an execution result.
Further, the system also comprises an execution pause unit, and in the test execution process, a pause instruction is obtained to pause the executing test.
Furthermore, the system also comprises a test plan modification unit, and when the test is not executed, the modification request is obtained, and the test plan is modified according to the page input information.
Further, the test plan includes a total test plan and a local test plan, and the system further includes an authority management unit configured to set a management authority of the test plan, where the management authority includes: the server has the authority of the whole test plan, and the test nodes have the authority of the local test plan.
A second aspect of the present invention provides a test management method, including the steps of:
acquiring a test requirement, and creating and storing a test plan according to the test requirement;
verifying the number of the executors, the configuration of the executors, the test cases and the test data in the test plan according to the verification rule;
after the test plan passes the verification, deploying a test environment, wherein the test environment comprises compiling and packaging according to a project source code path in the test plan, triggering a test node to deploy an execution machine, and carrying out FTP folder synchronization on the execution machine;
allocating execution machines according to a task execution list in a test plan, creating a task list of each execution machine, analyzing a task execution rule, calling a project script, executing the task list in a multithreading concurrent mode, and recording an execution result.
Further, the verification rule is specifically as follows:
the number of the execution machines and the configuration of the execution machines meet the requirement of executing each task;
whether the number of the execution machines meets the requirement of task concurrency;
scanning the FTP according to a project script path filled in by the test plan and a storage path of the test data, and checking whether the package is ready;
whether the test case in the test plan is in the project case library or not is tested;
if the conditions are all met, the test plan passes the verification, otherwise, the test plan fails the verification.
Further, the compiling and packaging according to the project source code path in the test plan specifically includes:
packing the project scripts, including compiling and packing project source codes, returning compiler information, updating project packing states and backing up the source codes and jar packages;
saving the script full path, including saving the compiled class file full path;
saving script constraint, including reading the script constraint information under the FTP constraint folder and saving the constraint information;
and verifying the test plan script, wherein the step of verifying whether the script required by the test plan has compiled error information or not and the step of verifying whether the full path of the class file of the script required by the test plan is missing or not are included.
Further, the deployment execution machine specifically includes:
analyzing the executive machine list, including reading and analyzing the executive machine number or executive machine IP list specified in the test plan;
deploying an AEP (Application enabling Platform), wherein AEP deployment is performed on the execution machines one by one or in batches, and deployment information is returned; if the deployment of the executive machine specified by the test plan fails, stopping the deployment and returning the failure deployment information; if the execution machines not specified by the test plan fail to be deployed, other execution machines are continuously deployed until the number of the execution machines meets the requirements of the test plan.
Further, the performing FTP folder synchronization on the execution machine specifically includes:
acquiring all contents of the FTP synchronous folder, synchronizing the deployed execution machines, and returning synchronous state and result information;
if the synchronization of the execution machine specified by the test plan fails, stopping the synchronization operation and returning error information;
if the synchronization of the execution machines specified by the non-test plan fails, the synchronous operation is continued until the number of the execution machines meets the requirements of the test plan.
The third aspect of the invention provides a test management platform, which comprises a server, test nodes, a tester and a database, wherein the server is connected with the database and is used for managing all test plans; the test nodes are used for managing a local test plan, and comprise creating the local test plan or acquiring the test plan from a database, verifying the test plan, deploying an execution machine according to the test plan and executing a local test, and storing the locally created and verified test plan to the database; the execution machine is used for executing the test plan.
The effect provided in the summary of the invention is only the effect of the embodiment, not all the effects of the invention, and one of the above technical solutions has the following advantages or beneficial effects:
according to the invention, a test management platform is set up, the test plan is stored in the database, the test plan is uniformly managed, the management disorder is avoided, the management authority is set, and the feasibility and the effectiveness of the test plan in the database are ensured. When the test is executed, the test plan to be executed is verified in sequence, the test environment is deployed and verified, and the test script is verified.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present invention, the drawings used in the description of the embodiments or prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
FIG. 1 is a schematic structural diagram of a test platform according to the present invention;
FIG. 2 is a schematic structural diagram of an embodiment 1 of the test system of the present invention;
FIG. 3 is a schematic structural diagram of embodiment 2 of the test system of the present invention;
FIG. 4 is a schematic flow chart of the test method of the present invention;
FIG. 5 is a flow chart of an embodiment of the testing method of the present invention.
Detailed Description
In order to clearly explain the technical features of the present invention, the following detailed description of the present invention is provided with reference to the accompanying drawings. The following disclosure provides many different embodiments, or examples, for implementing different features of the invention. To simplify the disclosure of the present invention, the components and arrangements of specific examples are described below. Furthermore, the present invention may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. It should be noted that the components illustrated in the figures are not necessarily drawn to scale. Descriptions of well-known components and processing techniques and procedures are omitted so as to not unnecessarily limit the invention.
As shown in fig. 1, the test platform of the present invention includes a server, a test node, a tester and a database, wherein the server is connected to the database and is used for managing all test plans; the test nodes are used for managing a local test plan, and comprise creating the local test plan or acquiring the test plan from a database, verifying the test plan, deploying an execution machine according to the test plan and executing a local test, and simultaneously storing the locally created and verified test plan into the database; the execution engine is used for execution of the test plan.
As shown in fig. 2, the test system of the present invention includes a test plan creation unit 1, a test plan verification unit 2, a test environment deployment unit 3, and a test script verification execution unit 4.
The test plan creating unit 1 makes a test plan according to the test requirements and stores the test plan in a database. The test plan comprises test basic information, a task execution list, execution case correlation information, a project script list, a responsible person and other data, and the test plan creating unit customizes the test plan according to a tested server or software or a created project.
The test plan verifying unit 2 verifies the test plan according to the verifying rule, and the verification object comprises the number of the executors, the configuration of the executors, the test cases and the test data. The verification of the test plan is to verify the feasibility of the test plan, and the verification state, the verification result and the verification content are stored in a verification node detail table before the test plan is executed, so that the current test plan can be conveniently checked.
And the test environment deployment unit 3 compiles and packages according to the project source code path in the test plan, triggers the test nodes to deploy the executors, and synchronizes FTP folders of the executors. The premise of the work of the environment deployment unit is that the test plan passes the verification.
The test script checking execution unit 4 allocates execution machines according to the task execution list in the test plan, creates a task list of each execution machine, analyzes the task execution rule, calls a project script, executes the task list in a multithreading concurrent manner, and records the execution result.
As shown in fig. 3, the test system further includes an execution suspension unit 5 and a test plan modification unit 6. The execution suspending unit 5 acquires a suspending instruction, suspends the test being executed, and modifies the test plan state to be suspended during the test execution. The test plan modification unit 6 obtains a modification request when the test is not executed (e.g., after suspension), and modifies the test plan according to the page input information.
The test plan comprises a whole test plan and a local test plan, and the test system further comprises an authority management unit for setting the management authority of the test plan. The management authority includes: the server has the authority of the whole test plan, and the test nodes have the authority of the local test plan.
As shown in fig. 4, the test management method of the present invention includes the following steps:
s1, acquiring a test requirement, and creating and storing a test plan according to the test requirement;
s2, verifying the number of executors, the configuration of the executors, the test cases and the test data in the test plan according to the verification rules;
s3, after the test plan passes the verification, deploying a test environment, including compiling and packaging according to a project source code path in the test plan, triggering a test node to deploy an execution machine, and carrying out FTP folder synchronization on the execution machine;
and S4, allocating execution machines according to the task execution list in the test plan, creating a task list of each execution machine, analyzing task execution rules, calling project scripts, executing the task list in a multithreading concurrent mode, and recording execution results.
The verification rule in step S2 is specifically: the number of the execution machines and the configuration of the execution machines meet the requirement of executing each task; whether the number of the execution machines meets the requirement of task concurrency; scanning the FTP according to a project script path filled in by the test plan and a storage path of the test data, and checking whether the package is ready; whether the test case in the test plan is in the project case library or not is tested; if the conditions are all met, the test plan passes the verification, otherwise, the test plan fails the verification.
In step S3, compiling and packaging according to the project source code path in the test plan specifically include: packing the project scripts, including compiling and packing project source codes, returning compiler information, updating project packing states and backing up the source codes and jar packages; saving the script full path, including saving the compiled class file full path; saving script constraint, including reading the script constraint information under the FTP constraint folder and saving the constraint information; and verifying the test plan script, wherein the step of verifying whether the script required by the test plan has compiled error information or not and the step of verifying whether the full path of the class file of the script required by the test plan is missing or not are included. And acquiring a project source code path input in the test plan, compiling and packaging, processing script compiling information, storing, and then automatically placing a jar packet folder printed by the project into a corresponding project/script under the synchronous folder. And the project source code and the printed jar package folder need to be backed up, namely, the backup source code and the printed jar package folder are put under the package version of the project corresponding to the backup folder. And scanning a public constraints folder in the source code folder, finding all script constraints stored under the project, and reading the constraints and storing data.
The deployment execution machine specifically comprises: analyzing the executive machine list, including reading and analyzing the executive machine number or executive machine IP list specified in the test plan; deploying AEP, including carrying out AEP deployment on the execution machines one by one or in batches and returning deployment information; if the deployment of the executive machine specified by the test plan fails, stopping the deployment and returning the failure deployment information; if the execution machines not specified by the test plan fail to be deployed, other execution machines are continuously deployed until the number of the execution machines meets the requirements of the test plan.
The specific implementation of FTP folder synchronization on the execution machine is as follows: acquiring all contents of the FTP synchronous folder, synchronizing the deployed execution machines, and returning synchronous state and result information; if the synchronization of the execution machine specified by the test plan fails, stopping the synchronization operation and returning error information; if the synchronization of the execution machines specified by the non-test plan fails, the synchronous operation is continued until the number of the execution machines meets the requirements of the test plan.
As shown in fig. 5, after the process starts, a test plan is selected and created or a test plan is selected from a test plan list of the database according to the test requirement, test plan verification, test environment deployment and test script verification are sequentially performed, and when the test plan verification fails or/and the test environment deploys different countries, error information is formed, and the current process is ended. A pause in testing may occur during the execution of the test script. The operation after the test is suspended comprises continuing to execute the test and modifying the test plan, if the test plan is modified, the verification of the test plan and the deployment of the test environment need to be carried out on the modified test plan again, and then the test can be executed. And the modification of the test plan may also exist when the test plan is selected from the test plan list.
The foregoing is only a preferred embodiment of the present invention, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the invention, and such modifications and improvements are also considered to be within the scope of the invention.
Claims (10)
1. A test management system, the system comprising:
the test plan creating unit is used for making a test plan according to the test requirements and storing the test plan into a database, wherein the test plan comprises test basic information, a task execution list, execution case correlation information and a project script list;
the test plan verification unit is used for verifying the test plan according to the verification rule, and the verification object comprises the number of the executors, the configuration of the executors, test cases and test data;
the test environment deployment unit is used for compiling and packaging according to a project source code path in the test plan, triggering the test node to deploy the executive machine and carrying out FTP folder synchronization on the executive machine;
the test script checking execution unit is used for distributing execution machines according to a task execution list in a test plan, creating a task list of each execution machine, analyzing a task execution rule, calling a project script, executing the task list in a multithreading concurrent mode and recording an execution result.
2. The test management system of claim 1, wherein the system further comprises an execution pause unit to obtain a pause instruction to pause the test being executed during the execution of the test.
3. The test management system according to claim 1, wherein the system further comprises a test plan modification unit which acquires a modification request when the test is not executed, and modifies the test plan based on the page input information.
4. A test management system according to any one of claims 1 to 3, wherein the test plan includes an entire test plan and a local test plan, the system further includes an authority management unit for setting management authority of the test plan, the management authority including: the server has the authority of the whole test plan, and the test nodes have the authority of the local test plan.
5. A test management method is characterized by comprising the following steps:
acquiring a test requirement, and creating and storing a test plan according to the test requirement;
verifying the number of the executors, the configuration of the executors, the test cases and the test data in the test plan according to the verification rule;
after the test plan passes the verification, deploying a test environment, wherein the test environment comprises compiling and packaging according to a project source code path in the test plan, triggering a test node to deploy an execution machine, and carrying out FTP folder synchronization on the execution machine;
allocating execution machines according to a task execution list in a test plan, creating a task list of each execution machine, analyzing a task execution rule, calling a project script, executing the task list in a multithreading concurrent mode, and recording an execution result.
6. The test management method according to claim 5, wherein the verification rule is specifically:
the number of the execution machines and the configuration of the execution machines meet the requirement of executing each task;
whether the number of the execution machines meets the requirement of task concurrency;
scanning the FTP according to a project script path filled in by the test plan and a storage path of the test data, and checking whether the package is ready;
whether the test case in the test plan is in the project case library or not is tested;
if the conditions are all met, the test plan passes the verification, otherwise, the test plan fails the verification.
7. The test management method according to claim 5, wherein the compiling and packing according to the project source code path in the test plan is specifically:
packing the project scripts, including compiling and packing project source codes, returning compiler information, updating project packing states and backing up the source codes and jar packages;
saving the script full path, including saving the compiled class file full path;
saving script constraint, including reading the script constraint information under the FTP constraint folder and saving the constraint information;
and verifying the test plan script, wherein the step of verifying whether the script required by the test plan has compiled error information or not and the step of verifying whether the full path of the class file of the script required by the test plan is missing or not are included.
8. The test management method according to claim 5, wherein the deployment execution machine is specifically:
analyzing the executive machine list, including reading and analyzing the executive machine number or executive machine IP list specified in the test plan;
deploying AEP, including carrying out AEP deployment on the execution machines one by one or in batches and returning deployment information; if the deployment of the executive machine specified by the test plan fails, stopping the deployment and returning the failure deployment information; if the execution machines not specified by the test plan fail to be deployed, other execution machines are continuously deployed until the number of the execution machines meets the requirements of the test plan.
9. The test management method according to claim 5, wherein the FTP folder synchronization performed on the execution machine is specifically:
acquiring all contents of the FTP synchronous folder, synchronizing the deployed execution machines, and returning synchronous state and result information;
if the synchronization of the execution machine specified by the test plan fails, stopping the synchronization operation and returning error information;
if the synchronization of the execution machines specified by the non-test plan fails, the synchronous operation is continued until the number of the execution machines meets the requirements of the test plan.
10. A test management platform is characterized by comprising a server, test nodes, a tester and a database, wherein the server is connected with the database and used for managing all test plans; the test nodes are used for managing a local test plan, and comprise creating the local test plan or acquiring the test plan from a database, verifying the test plan, deploying an execution machine according to the test plan and executing a local test, and storing the locally created and verified test plan to the database; the execution machine is used for executing the test plan.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911088952.2A CN110990261A (en) | 2019-11-08 | 2019-11-08 | Test management system, method and platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911088952.2A CN110990261A (en) | 2019-11-08 | 2019-11-08 | Test management system, method and platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN110990261A true CN110990261A (en) | 2020-04-10 |
Family
ID=70083856
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911088952.2A Pending CN110990261A (en) | 2019-11-08 | 2019-11-08 | Test management system, method and platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110990261A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112230627A (en) * | 2020-10-30 | 2021-01-15 | 重庆长安汽车股份有限公司 | Remote testing method of vehicle body controller |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530231A (en) * | 2013-10-12 | 2014-01-22 | 北京京东尚科信息技术有限公司 | Application program testing method and system based on service process control |
| CN105446878A (en) * | 2015-11-09 | 2016-03-30 | 上海爱数信息技术股份有限公司 | Continuous program automated testing method |
| US20170153967A1 (en) * | 2014-02-06 | 2017-06-01 | B. G. Negev Technologies And Applications Ltd., At Ben-Gurion University | Using model-based diagnosis to improve software testing |
| CN106844198A (en) * | 2016-12-27 | 2017-06-13 | 浪潮软件集团有限公司 | Distributed dispatching automation test platform and method |
| CN107463362A (en) * | 2016-06-03 | 2017-12-12 | 北京京东尚科信息技术有限公司 | The method and system of lasting deployment based on multiple Jenkins |
| CN107783900A (en) * | 2017-09-22 | 2018-03-09 | 郑州云海信息技术有限公司 | A kind of efficient server system test and management system and method |
| CN109086216A (en) * | 2018-10-26 | 2018-12-25 | 苏州友教习亦教育科技有限公司 | Automatization test system |
| CN109086213A (en) * | 2018-09-10 | 2018-12-25 | 汽解放汽车有限公司 | A kind of commercial vehicle network test management system and method based on distributed system |
| CN109766269A (en) * | 2018-12-18 | 2019-05-17 | 微梦创科网络科技（中国）有限公司 | Continuous integrating automated testing method, device, equipment and medium |
-
2019
- 2019-11-08 CN CN201911088952.2A patent/CN110990261A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103530231A (en) * | 2013-10-12 | 2014-01-22 | 北京京东尚科信息技术有限公司 | Application program testing method and system based on service process control |
| US20170153967A1 (en) * | 2014-02-06 | 2017-06-01 | B. G. Negev Technologies And Applications Ltd., At Ben-Gurion University | Using model-based diagnosis to improve software testing |
| CN105446878A (en) * | 2015-11-09 | 2016-03-30 | 上海爱数信息技术股份有限公司 | Continuous program automated testing method |
| CN107463362A (en) * | 2016-06-03 | 2017-12-12 | 北京京东尚科信息技术有限公司 | The method and system of lasting deployment based on multiple Jenkins |
| CN106844198A (en) * | 2016-12-27 | 2017-06-13 | 浪潮软件集团有限公司 | Distributed dispatching automation test platform and method |
| CN107783900A (en) * | 2017-09-22 | 2018-03-09 | 郑州云海信息技术有限公司 | A kind of efficient server system test and management system and method |
| CN109086213A (en) * | 2018-09-10 | 2018-12-25 | 汽解放汽车有限公司 | A kind of commercial vehicle network test management system and method based on distributed system |
| CN109086216A (en) * | 2018-10-26 | 2018-12-25 | 苏州友教习亦教育科技有限公司 | Automatization test system |
| CN109766269A (en) * | 2018-12-18 | 2019-05-17 | 微梦创科网络科技（中国）有限公司 | Continuous integrating automated testing method, device, equipment and medium |
Non-Patent Citations (6)
| Title |
|---|
| ZEKYLL: "第一条Android自动化测试脚本", 《HTTPS://BLOG.CSDN.NET/HZK594512323/ARTICLE/DETAILS/91815963》 * |
| 冯灵霞: "《软件测试计划》", 31 January 2017, 西安电子科技大学出版社 * |
| 孟磊: "《软件质量与测试》", 30 April 2015, 西安电子科技大学出版社 * |
| 张善文: "《软件测试及其案例分析》", 31 December 2012, 西安电子科技大学出版社 * |
| 杨晶洁: "《现代软件工程应用技术》", 31 May 2017, 北京理工大学出版社 * |
| 林勤花等: "《企业案例软件测试技术》", 30 September 2015, 西南交通大学出版社 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112230627A (en) * | 2020-10-30 | 2021-01-15 | 重庆长安汽车股份有限公司 | Remote testing method of vehicle body controller |
| CN112230627B (en) * | 2020-10-30 | 2022-10-11 | 重庆长安汽车股份有限公司 | Remote testing method of vehicle body controller |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109960643B (en) | Code testing method and device | |
| CN110187914B (en) | Application development method, system and device | |
| US9189227B2 (en) | Systems, methods, and computer program products for a software build and load process using a compilation and deployment service | |
| US8510717B2 (en) | Method and system for testing application modules using static tests from a test suite | |
| CN113703730A (en) | Continuous integration method and device, computer equipment and storage medium | |
| US7512933B1 (en) | Method and system for associating logs and traces to test cases | |
| US20070240134A1 (en) | Software packaging model supporting multiple entity types | |
| US20110178788A1 (en) | Predicate Checking for Distributed Systems | |
| CN109902005B (en) | Automatic testing method and system | |
| CN105988798B (en) | Patch processing method and device | |
| US20190073292A1 (en) | State machine software tester | |
| US9317254B1 (en) | Fault tolerance model, methods, and apparatuses and their validation techniques | |
| CN111158655A (en) | Deployment method and device of software running environment | |
| Meiklejohn et al. | Service-level fault injection testing | |
| CN110990261A (en) | Test management system, method and platform | |
| Susskraut et al. | Automatically finding and patching bad error handling | |
| CN110688147A (en) | Method for packing and analyzing metadata | |
| Talwar et al. | Comparison of approaches to service deployment | |
| Mascheroni et al. | Identifying key success factors in stopping flaky tests in automated REST service testing | |
| Pautasso | JOpera: An agile environment for web service composition with visual unit testing and refactoring | |
| Silva et al. | Experience report: orthogonal classification of safety critical issues | |
| CN111831554A (en) | Code checking method and device | |
| Ma et al. | Analyzing distributed Java applications by automatic centralization | |
| CN111367796B (en) | Application program debugging method and device | |
| CN115543838A (en) | Code scanning rule processing method and device, storage medium and electronic equipment |
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: 20200410 |
|
| RJ01 | Rejection of invention patent application after publication |