[go: up one dir, main page]

CN110069414B - Regression testing method and system - Google Patents

Regression testing method and system Download PDF

Info

Publication number
CN110069414B
CN110069414B CN201910339873.8A CN201910339873A CN110069414B CN 110069414 B CN110069414 B CN 110069414B CN 201910339873 A CN201910339873 A CN 201910339873A CN 110069414 B CN110069414 B CN 110069414B
Authority
CN
China
Prior art keywords
test
test case
model
case library
baseline
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.)
Active
Application number
CN201910339873.8A
Other languages
Chinese (zh)
Other versions
CN110069414A (en
Inventor
王彤
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Geely Holding Group Co Ltd
Geely Automobile Research Institute Ningbo Co Ltd
Original Assignee
Zhejiang Geely Holding Group Co Ltd
Geely Automobile Research Institute Ningbo Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Zhejiang Geely Holding Group Co Ltd, Geely Automobile Research Institute Ningbo Co Ltd filed Critical Zhejiang Geely Holding Group Co Ltd
Priority to CN201910339873.8A priority Critical patent/CN110069414B/en
Publication of CN110069414A publication Critical patent/CN110069414A/en
Application granted granted Critical
Publication of CN110069414B publication Critical patent/CN110069414B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Prevention of errors by analysis, debugging or testing of software
    • G06F11/3668Testing of software
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30Computing systems specially adapted for manufacturing

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)
  • Testing Or Calibration Of Command Recording Devices (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention provides a regression testing method and a regression testing system, and relates to the technical field of testing. In the regression testing method, firstly, automatically identifying and deleting the non-reusable test cases in the initial baseline test case library; then obtaining a test case to be updated corresponding to the model change part in an initial baseline test case library; secondly, modifying the test cases to be updated according to the new model functions and test requirements, and generating a final baseline test case library; and finally, running a final baseline test case library to realize regression testing. By adopting the method, the test cases of the baseline test case library are automatically divided into three types, namely, no modification and no reusability. The tester does not need to spend effort to arrange the original test cases, so that the writing efficiency of the test cases is greatly improved, and the growth speed of the test cases can be effectively reduced.

Description

Regression testing method and system
Technical Field
The invention relates to the technical field of testing, in particular to a regression testing method and system.
Background
Model-based development refers to a development mode, i.e., an algorithm is implemented in the form of a model, such as a MATLAB/Simulink model. The graphical programming mode makes engineers pay more attention to algorithms rather than programming languages in the software development of the automobile field based on model development, meanwhile, the developed model is more readable, and early verification and document management of the model are more convenient than that of traditional handwriting codes. Software testing is also becoming increasingly automated as an important element in model-based development, and various automated testing approaches are emerging.
After the model test passes verification, there are many version iterations, and regression test is needed after each version iteration, so as to confirm that no new errors or other model errors are introduced after each model update. Regression testing is an important part of the life cycle of software, and how to improve the efficiency of regression testing is a technical problem that those skilled in the art are urgent to solve.
Disclosure of Invention
The invention aims to provide a regression testing method and a regression testing system, which are used for solving the problems of low regression testing efficiency and high cost.
The invention further aims to automatically screen, modify and delete the last baseline test case library, automatically save the test cases and test results after the test is completed, form a new baseline test case library, greatly improve the writing efficiency of the test cases and reduce the growth speed of the test cases.
In one aspect, the present invention provides a regression testing method comprising:
identifying and deleting non-reusable test cases in the initial baseline test case library;
acquiring a test case to be updated corresponding to a model change part in the initial baseline test case library;
modifying the test cases to be updated according to new model functions and test requirements, and generating a final baseline test case library;
and running the final baseline test case library to realize regression testing.
Optionally, the identifying and deleting the non-reusable test cases in the initial baseline test case library includes:
judging whether a part of the models is changed or not, wherein the part of the models is changed, and the change of the part of the models comprises at least one of the number, the sequence and the definition of the input/output interfaces of the part of the models;
if the partial model is changed, judging that the test case corresponding to the partial model is a non-reusable test case.
Optionally, the obtaining the test case to be updated corresponding to the model change part in the initial baseline test case library includes:
operating the initial baseline test case after deleting the non-multiplexing test case;
judging the coverage of the rest reusable test cases;
and if the coverage is not zero, judging that the current reusable test case covers the changed model.
Optionally, after the modifying the test case to be updated according to the new model function and the test requirement, the method further includes:
and adding new test cases into the modified baseline test case library to form a final baseline test case library.
Optionally, the running the final baseline test case library to implement a regression test includes:
storing the final baseline test case library into Excel data;
reading the Excel data, and automatically calling an API of a toolbox of the Simulink to correspond the input and the output of the test case with the input and the output of the model;
automatically executing MIL simulation after the test case is imported, and obtaining a test result of MIL simulation;
automatically generating codes by the model, and then executing SIL simulation to obtain a test result of the SIL simulation;
automatically comparing an expected output result written by the test case, an output result of MIL simulation and an output result of SIL simulation, and judging whether errors among the three are within a given error range;
generating a test report according to the simulation result, the state, the decision, the coverage report, the software version information and the model summary information;
if the test report is qualified, automatically storing the test case and the test result of the test to form a new baseline test case library.
Optionally, before deleting the non-reusable test cases in the initial baseline test case library, the method further comprises:
selecting a model or a subsystem in the model according to the test requirement, automatically calling an interface function of a toolbox of the Simulink, generating a test framework for a test object, and storing the test framework into a new file;
selecting and loading variables necessary for model simulation and code generation to a MATLAB working area;
and reading an initial baseline test case library.
In another aspect, the present invention also provides a regression testing system, including:
the processing unit is used for identifying and deleting the non-reusable test cases in the initial baseline test case library;
the acquisition unit is used for acquiring to-be-updated test cases corresponding to the model change part in the initial baseline test case library;
the correction unit is used for correcting the test cases to be updated according to the new model functions and the test requirements and generating a final baseline test case library;
and the operation unit is used for operating the final baseline test case library to realize regression test.
Optionally, the processing unit is further configured to determine that the test case corresponding to the partial model is an unreusable test case when the partial model is changed, wherein,
the partial model changes including, but not limited to, at least one of the number, order, and definition of its input-output interfaces.
Optionally, the obtaining unit is further configured to determine, when the initial baseline test case from which the non-reusable test case is deleted is executed, a reusable test case covering the altered model.
Optionally, the method further comprises:
and the adding unit is used for adding new test cases into the modified baseline test case library to form a final baseline test case library.
The regression testing method of the invention firstly automatically identifies and deletes the non-multiplexing test cases in the initial baseline test case library; then obtaining a test case to be updated corresponding to the model change part in an initial baseline test case library; secondly, modifying the test cases to be updated according to the new model functions and test requirements, and generating a final baseline test case library; and finally, running a final baseline test case library to realize regression testing. By adopting the method, the test cases of the baseline test case library are automatically divided into three types, namely, no modification and no reusability. Screening, modifying and deleting the last baseline test case library, and automatically storing the test cases and test results after the test is completed to form a new baseline test case library. The tester does not need to spend effort to arrange the original test cases, so that the writing efficiency of the test cases is greatly improved, and the growth speed of the test cases can be effectively reduced.
The above, as well as additional objectives, advantages, and features of the present invention will become apparent to those skilled in the art from the following detailed description of a specific embodiment of the present invention when read in conjunction with the accompanying drawings.
Drawings
Some specific embodiments of the invention will be described in detail hereinafter by way of example and not by way of limitation with reference to the accompanying drawings. The same reference numbers will be used throughout the drawings to refer to the same or like parts or portions. It will be appreciated by those skilled in the art that the drawings are not necessarily drawn to scale. In the accompanying drawings:
FIG. 1 is a schematic flow chart of a regression testing method according to one embodiment of the invention;
FIG. 2 is a schematic flow chart of a regression testing method according to another embodiment of the invention;
FIG. 3 is a schematic system diagram of a regression testing system according to one embodiment of the invention.
The reference numerals in the figures are:
1-processing unit, 2-acquisition unit, 3-correction unit, 4-running unit.
Detailed Description
FIG. 1 is a schematic flow chart of a regression testing method according to one embodiment of the invention. Fig. 2 is a schematic flow chart of a regression testing method according to another embodiment of the invention. FIG. 3 is a schematic system diagram of a regression testing system according to one embodiment of the invention. The regression testing method and system according to the embodiment of the present invention are described below with reference to fig. 1 to 3.
Referring to fig. 1, the regression testing method in the present embodiment includes:
step S101, automatically identifying and deleting non-reusable test cases in an initial baseline test case library;
step S102, obtaining a test case to be updated corresponding to a model change part in an initial baseline test case library;
step S103, modifying the test cases to be updated according to the new model functions and the test requirements, and generating a final baseline test case library;
and step S104, running a final baseline test case library to realize regression testing.
By adopting the method, the test cases of the baseline test case library are automatically divided into three types, namely, no modification and no reusability. Screening, modifying and deleting the last baseline test case library, and automatically storing the test cases and test results after the test is completed to form a new baseline test case library. The tester does not need to spend effort to arrange the original test cases, so that the writing efficiency of the test cases is greatly improved, and the growth speed of the test cases can be effectively reduced.
Further, in the present embodiment, identifying and deleting the non-reusable test cases in the initial baseline test case library includes:
judging whether a part of the models are changed or not, wherein the part of the models are changed, and the change of the part of the models comprises at least one of the number, the sequence and the definition of the input/output interfaces of the part of the models;
if part of the model is changed, judging that the test case corresponding to the model is a non-reusable test case.
Further, in this embodiment, obtaining the test case to be updated corresponding to the model change portion in the initial baseline test case library includes:
operating the initial baseline test case after deleting the non-reusable test case;
judging the coverage of the rest reusable test cases;
if the coverage is not zero, the current reusable test case is judged to cover the changed model.
In a further embodiment, after modifying the test case to be updated according to the new model function and the test requirement, the method further comprises:
and adding new test cases into the modified baseline test case library to form a final baseline test case library.
Further, in the present embodiment, running the final baseline test case library to implement the regression test includes:
storing the final baseline test case library into Excel data;
reading Excel data, and automatically calling an API of a toolbox of the Simulink to correspond the input and the output of the test case to the input and the output of the model;
automatically executing MIL simulation after the test cases are imported, and obtaining test results of MIL simulation;
automatically generating codes by the model, and then executing SIL simulation to obtain a test result of the SIL simulation;
automatically comparing an expected output result written by the test case, an output result of MIL simulation and an output result of SIL simulation, and judging whether errors among the three are within a given error range;
generating a test report according to the simulation result, the state, the decision, the coverage report, the software version information and the model summary information;
if the test report is qualified, automatically storing the test case and the test result of the test to form a new baseline test case library.
Further, in one embodiment, before deleting the non-reusable test cases in the initial baseline test case library, further comprises:
selecting a model or a subsystem in the model according to the test requirement, automatically calling an interface function of a toolbox of the Simulink, generating a test framework for a test object, and storing the test framework into a new file;
selecting and loading variables necessary for model simulation and code generation to a MATLAB working area;
and reading an initial baseline test case library.
Referring to fig. 2 and 3, the regression testing system in the present embodiment includes a processing unit 1, an acquisition unit 2, a correction unit 3, and an operation unit 4. The processing unit 1 is used for identifying and deleting the non-reusable test cases in the initial baseline test case library. The obtaining unit 2 is used for obtaining the test case to be updated corresponding to the model changing part in the initial baseline test case library. The correction unit 3 is used for modifying the test cases to be updated according to the new model functions and the test requirements, and generating a final baseline test case library. The operation unit 4 is used for operating the final baseline test case library to realize regression testing.
In the present embodiment, the processing unit 1 is further configured to:
judging whether a part of the models are changed or not, wherein the part of the models are changed, and the change of the part of the models comprises at least one of the number, the sequence and the definition of the input/output interfaces of the part of the models;
if part of the model is changed, judging that the test case corresponding to the model is a non-reusable test case.
In the present embodiment, the acquisition unit 2 is further configured to:
running an initial baseline test case from which the non-reusable test case is deleted;
judging the coverage of the reusable test cases;
if the coverage is not zero, the current test case is judged to cover the changed model.
In a further embodiment, the regression testing system further comprises:
and the adding unit is used for adding new test cases into the modified baseline test case library to form a final baseline test case library.
Referring to fig. 2, the test method of the regression testing system is described in detail below:
1) According to the test requirement, selecting a model or a subsystem in the model, automatically calling an API (interface function) of a toolbox SimulinkTestTool of Simulink, generating a TestHarness (test framework) for a test object, and storing the test framework into a new file.
2) And selecting and loading variables necessary for model simulation and code generation into a MATLAB working area, wherein the variables can be stored in a mats or m file.
3) When the baseline test case library is not available (such as the first version of software test), the names of input (Inport) and input (Outport) modules at the top layer of the model to be tested are automatically read, a test case template is generated, and a tester writes the test case according to the corresponding names of the input and the output.
4) If a baseline test case library exists, automatically identifying whether the test cases cannot be reused due to the input and output changes of the model, wherein the test cases cannot be reused due to the changes of the input and output quantity, the sequence, the definition and the like. And the input and output in the reading model are compared with a base line test case library, and the test case which is not available for multiplexing is obtained if the input and output names are not available for multiplexing, and the test case which is not available for multiplexing is deleted.
5) For the reusable test cases, the test model of the current version is automatically operated once, and the coverage of the reusable test cases to the current test model is obtained. When one test case does not cover the model of the changed part, no modification is needed; when the model covering the changed part is used, the test cases are listed, and the tester modifies, adds and deletes the test cases according to the changed model and the new test requirements.
6) The new test case set is obtained through the steps, and is stored in an Excel form. Reading data in Excel, and automatically calling an API of a toolbox SimulinkTestTool of Simulink to correspond input and output of a test case to input and output of a model.
7) And automatically executing MIL (Model inLoop) simulation after the test cases are imported, and obtaining the test result of MIL simulation.
8) And automatically generating codes by the test model, and executing SIL (SoftwareinLoop) simulation to obtain a test result of SIL simulation.
9) And automatically comparing whether the expected output written by the test case, the output of the MIL simulation and the output of the SIL simulation are within a given error range, and if so, passing the test.
10 Reading simulation results, conditions, decision coverage reports, software version information and model summary information to generate a test report.
11 If the test passes and the release software is confirmed, automatically storing the test case and the test result of the test to form a new base line test case library.
In the regression testing system in the above embodiment, the partial codes are as follows:
SelectSystem (); % selection of model to be tested
LoadParameter (); % load data
CheckTestCaseLib (); % inspection test cases
LoadTestCase (); % load test cases
SimModel (); % MIL simulation
Genetecode (); % code generated
SimCode (); % SIL simulation
Genereport (); % generate test report
After the software of a baseline version is formed, the test cases and test results of the baseline version software are automatically saved to be used as a baseline test case library of the regression test after the next version iteration, after the second version of software, the test cases of the baseline test case library of the last time are automatically classified into three types of no need of modification, no need of modification and no reusability aiming at the model after the iteration, the test cases are screened, modified and deleted, and the test cases and the test results are automatically saved after the test is completed to form a new baseline test case library.
Further, the original solution needs to sort the test cases of the previous version by itself, and manual analysis needs to prune which test cases and modify which test cases, which are complicated. In the above embodiment, when the model changes, test cases in the original baseline test case library, which cannot be reused due to the interface change, are screened, and then the reusable test cases are classified into two types, namely, no modification is required and no modification is required, according to whether the original test cases cover the modified model. Therefore, the test case writing efficiency of the regression test can be effectively improved. The test cases and results of the previous test are used as references, and a part of repeated work is reduced. Meanwhile, test cases which are not required to be modified, modified and reused are automatically distinguished, and testers do not need to spend effort to arrange the original test cases, so that the writing efficiency of the test cases is greatly improved.
In addition, the system and the method can automatically distinguish the test cases to be modified, and part of the test cases come from modifying the original test cases, so that the growth speed of the test cases can be effectively reduced.
By now it should be appreciated by those skilled in the art that while a number of exemplary embodiments of the invention have been shown and described herein in detail, many other variations or modifications of the invention consistent with the principles of the invention may be directly ascertained or inferred from the present disclosure without departing from the spirit and scope of the invention. Accordingly, the scope of the present invention should be understood and deemed to cover all such other variations or modifications.

Claims (8)

1. A regression testing method, comprising:
identifying and deleting non-reusable test cases in the initial baseline test case library;
acquiring a test case to be updated corresponding to a model change part in the initial baseline test case library;
modifying the test cases to be updated according to new model functions and test requirements, and adding new test cases into the modified baseline test case library to form a final baseline test case library;
running the final baseline test case library to realize regression testing;
the obtaining the test case to be updated corresponding to the model change part in the initial baseline test case library comprises the following steps:
operating the initial baseline test case after deleting the non-multiplexing test case;
judging the coverage of the rest reusable test cases;
if the coverage is not zero, judging that the current reusable test case covers the changed model; screening out test cases which cannot be reused due to interface variation in the reusable baseline test case library, and classifying the reusable test cases into two types which are not required to be modified and are required to be modified according to whether the reusable test cases cover the modified model.
2. The regression testing method of claim 1, wherein,
the identifying and deleting the non-reusable test cases in the initial baseline test case library comprises the following steps:
judging whether a part of the models is changed or not, wherein the part of the models is changed, and the change of the part of the models comprises at least one of the number, the sequence and the definition of the input/output interfaces of the part of the models;
if the partial model is changed, judging that the test case corresponding to the partial model is a non-reusable test case.
3. The regression testing method of claim 1, wherein,
running the final baseline test case library to implement a regression test includes:
storing the final baseline test case library into Excel data;
reading the Excel data, and automatically calling an API of a toolbox of the Simulink to correspond the input and the output of the test case with the input and the output of the model;
automatically executing MIL simulation after the test case is imported, and obtaining a test result of MIL simulation;
automatically generating codes by the model, and then executing SIL simulation to obtain a test result of the SIL simulation;
automatically comparing an expected output result written by the test case, an output result of MIL simulation and an output result of SIL simulation, and judging whether errors among the three are within a given error range;
generating a test report according to the simulation result, the state, the decision, the coverage report, the software version information and the model summary information;
if the test report is qualified, automatically storing the test case and the test result of the test to form a new baseline test case library.
4. The regression testing method of claim 1, wherein,
before deleting the non-reusable test cases in the initial baseline test case library, the method further comprises:
selecting a model or a subsystem in the model according to the test requirement, automatically calling an interface function of a toolbox of the Simulink, generating a test framework for a test object, and storing the test framework into a new file;
selecting and loading variables necessary for model simulation and code generation to a MATLAB working area;
and reading an initial baseline test case library.
5. A regression testing system, comprising:
the processing unit is used for identifying and deleting the non-reusable test cases in the initial baseline test case library;
the acquisition unit is used for acquiring to-be-updated test cases corresponding to the model change part in the initial baseline test case library;
the correction unit is used for correcting the test cases to be updated according to the new model functions and the test requirements and generating a final baseline test case library;
and the operation unit is used for operating the final baseline test case library to realize regression test.
6. The regression testing system of claim 5, wherein,
the processing unit is further configured to determine that the test case corresponding to the model is a non-reusable test case when a part of the model is changed, wherein,
the partial model changes including, but not limited to, at least one of the number, order, and definition of its input-output interfaces.
7. The regression testing system of claim 5, wherein,
the acquisition unit is further configured to determine that the test case covering the changed model is a reusable test case when the initial baseline test case from which the non-reusable test case was deleted is run.
8. The regression testing system of claim 5, further comprising:
and the adding unit is used for adding new test cases into the modified baseline test case library to form a final baseline test case library.
CN201910339873.8A 2019-04-25 2019-04-25 Regression testing method and system Active CN110069414B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910339873.8A CN110069414B (en) 2019-04-25 2019-04-25 Regression testing method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910339873.8A CN110069414B (en) 2019-04-25 2019-04-25 Regression testing method and system

Publications (2)

Publication Number Publication Date
CN110069414A CN110069414A (en) 2019-07-30
CN110069414B true CN110069414B (en) 2023-05-30

Family

ID=67368850

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910339873.8A Active CN110069414B (en) 2019-04-25 2019-04-25 Regression testing method and system

Country Status (1)

Country Link
CN (1) CN110069414B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7225064B2 (en) * 2019-09-12 2023-02-20 株式会社日立ソリューションズ Simulation method and simulation program
CN111858292B (en) * 2019-09-12 2024-11-12 北京嘀嘀无限科技发展有限公司 Test case screening method, screening system, computer equipment and storage medium
CN113254325A (en) * 2020-02-10 2021-08-13 北京沃东天骏信息技术有限公司 Test case processing method and device
CN115840704A (en) * 2022-12-12 2023-03-24 之江实验室 Simulation software testing method and device, storage medium and electronic equipment

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102135937A (en) * 2011-03-15 2011-07-27 西安邮电学院 Pairwise overlay integrated software test case suite generating method
JP2014026458A (en) * 2012-07-26 2014-02-06 Toshiba Corp Test case generation support device
CN103577311A (en) * 2012-07-26 2014-02-12 深圳市世纪光速信息技术有限公司 Method and device for screening test cases
GB2508643A (en) * 2012-12-07 2014-06-11 Ibm Method for Performing a Regression Test after Modifying Source Code File
CN106933728A (en) * 2015-12-29 2017-07-07 中国移动(深圳)有限公司 The method and device of demand and use-case relevance metric

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6782518B2 (en) * 2002-03-28 2004-08-24 International Business Machines Corporation System and method for facilitating coverage feedback testcase generation reproducibility
JP4956131B2 (en) * 2006-10-06 2012-06-20 シャープ株式会社 Biometric authentication device and method, and biometric authentication processing program
CN103034227A (en) * 2012-09-20 2013-04-10 北京智行鸿远汽车技术有限公司 Testing method in circuit of battery electric vehicle vehicle-control unit model
US20140245264A1 (en) * 2013-02-28 2014-08-28 International Business Machines Corporation Identifying Test Cases Based on Changed Test Code
US9311223B2 (en) * 2013-05-21 2016-04-12 International Business Machines Corporation Prioritizing test cases using multiple variables
US20150026664A1 (en) * 2013-07-17 2015-01-22 International Business Machines Corporation Method and system for automated test case selection
GB2530516A (en) * 2014-09-24 2016-03-30 Ibm Intelligent Software Test Augmenting
CN104391791B (en) * 2014-11-21 2018-01-19 北京经纬恒润科技有限公司 The method of testing and device of embedded Control algorithm
CN106557413A (en) * 2015-09-25 2017-04-05 伊姆西公司 Based on the method and apparatus that code coverage obtains test case
CN107729727B (en) * 2016-08-11 2021-03-02 腾讯科技(深圳)有限公司 Real-name authentication method and device for account
CN108076018A (en) * 2016-11-16 2018-05-25 阿里巴巴集团控股有限公司 Identity authorization system, method, apparatus and account authentication method
CN107944378A (en) * 2017-11-20 2018-04-20 广东金赋科技股份有限公司 The personal identification method and self-help serving system of a kind of Self-Service

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102135937A (en) * 2011-03-15 2011-07-27 西安邮电学院 Pairwise overlay integrated software test case suite generating method
JP2014026458A (en) * 2012-07-26 2014-02-06 Toshiba Corp Test case generation support device
CN103577311A (en) * 2012-07-26 2014-02-12 深圳市世纪光速信息技术有限公司 Method and device for screening test cases
GB2508643A (en) * 2012-12-07 2014-06-11 Ibm Method for Performing a Regression Test after Modifying Source Code File
CN106933728A (en) * 2015-12-29 2017-07-07 中国移动(深圳)有限公司 The method and device of demand and use-case relevance metric

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
软件回归测试用例选取方法研究;王小丽;段永颢;;空间控制技术与应用(03);全文 *

Also Published As

Publication number Publication date
CN110069414A (en) 2019-07-30

Similar Documents

Publication Publication Date Title
CN110069414B (en) Regression testing method and system
CN109840206B (en) Data testing method, device, terminal and storage medium
CN103631720B (en) The generation method and apparatus of test case
CN109189479B (en) Parallel automatic verification method for processor instruction set
CN111897727A (en) Software testing method and device, computer equipment and storage medium
CN112131116B (en) Automatic regression testing method for embedded software
CN113360388B (en) Method for integrally managing test process of unmanned aerial vehicle ground station software
CN112181854A (en) Method, device, equipment and storage medium for generating flow automation script
CN114924737A (en) Battery management system source code integration test method and device and electronic equipment
US7895575B2 (en) Apparatus and method for generating test driver
US10642716B1 (en) Automated software program repair
CN113742249B (en) Test script granulation method and system based on desktop operating system
CN114661615A (en) FPGA software testing method and device
JP7557431B2 (en) Apparatus and method for supporting source code modification
CN101673200B (en) The detection method of user input model and device
CN112395199B (en) Distributed software instance testing method based on cloud computing and software development platform
CN110928760A (en) Unit testing method and device in embedded system
US10761962B1 (en) Automated software program repair
CN114448851B (en) Automatic data testing method and system
US11740895B2 (en) Generation of software program repair explanations
CN112580282B (en) Method, apparatus, device and storage medium for integrated circuit design verification
CN116257442A (en) A test method and system for AUTOSAR operating system based on decision table
CN115268403A (en) A vehicle EOL automated testing method
CN116610551A (en) Code coverage rate calculation method, device, equipment and medium
KR20230014333A (en) Vehicle controller test device and method therefor

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
GR01 Patent grant
GR01 Patent grant