CN107391376A - A kind of regression testing method - Google Patents
A kind of regression testing method Download PDFInfo
- Publication number
- CN107391376A CN107391376A CN201710615391.1A CN201710615391A CN107391376A CN 107391376 A CN107391376 A CN 107391376A CN 201710615391 A CN201710615391 A CN 201710615391A CN 107391376 A CN107391376 A CN 107391376A
- Authority
- CN
- China
- Prior art keywords
- case
- testing method
- establish
- bug
- uses case
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The present invention relates to software testing technology field, discloses a kind of regression testing method.Specifically include procedure below：Step 1: being screened to use-case, set of uses case is established；Step 2: establish use-case set of uses case automation use-case interface multiple mapping relation；Step 3: establish set of uses case milestone；Step 4: quantify set of uses case intersection degree and multiple mapping rate.Based on service logic combination and bug Analysis and Screening sets of uses case；Reduce the complexity that tradition screens use-case based on function and path analysis mode；Path coverage is lifted, reduces use-case intersection degree；Multiple mapping relation is established, improves use-case reusability, the efficiency of lifting structure automatic returning, whole regression test process optimization；Set of uses case execution priority, classification；Control scheduling use-case implementation procedure, execution efficiency, performs time-consuming, set of uses case milestone；Contribute to the bug of issue to find in advance, beneficial to successive ignition, reduce regression test cost, lift bug ability of discovery.
Description
Technical field
The present invention relates to software testing technology field, particularly a kind of regression testing method.
Background technology
With increasingly lifting of the development and market of software engineering to software requirement, the scale of software is increasing, software
Complexity it is bigger, it is stricter to the quality requirement of software product.The iteration frequency of version is also more next in software development process
It is faster, it is higher to the quality and efficiency requirements of regression test.Traditional software regression testing method is focused on passing through appellative function point
Change either test path or test scene refine regression test case.Caused problem is that use-case reusing degree is low；Base
It is not easy to implement and promotes in the use-case triage techniques threshold height of function level, only focuses on use-case and do not focus on controlling implementation procedure etc. existing
As.It is uncontrollable so as to cause regression test unreliable, the problems such as efficiency is low.
The content of the invention
The technical problems to be solved by the invention are：For above-mentioned problem, there is provided a kind of software regression testing
Method.
The technical solution adopted by the present invention is as follows：A kind of software regression testing method, specifically includes procedure below：It is Step 1: right
Use-case is screened, and establishes set of uses case；Step 2: establish use-case-set of uses case-automation use-case interface multiple mapping relation；Step
Rapid three, set of uses case milestone is established；Step 4: quantify set of uses case intersection degree and multiple mapping rate.
Further, the detailed process of above-mentioned steps one is：Step 11, according to service logic carry out use-case classification；Step
12nd, the science and correctness of classification and classification are verified according to bug analysis results, further carries out use-case classification；Step 13, again
Carry out establishing set of uses case according to use-case classification.
Further, above-mentioned bug analysis includes analyzing the failure occurred in integration testing and system testing, also or
The produced problem of design aspect is analyzed.
Further, the detailed process of above-mentioned steps two is：Step 21, the characteristics of being classified according to use-case, return related example
Class, regression test case is combined into according to business characteristic；Step 22, calculate set of uses case mapping rate；Step 23, reflected according to set of uses case
Penetrate rate screening, combination regression test case；Step 24, according to set of uses case by use-case business, use-case flow, three layers points of use-case data
Collection, form automation use-case interface；Step 25, establish use-case-set of uses case-automation use-case interface multiple mapping relation.
Further, the detailed process of above-mentioned steps three is：Step 31, division set of uses case execution priority；Step 32, root
According to set of uses case execution priority, control scheduling use-case implementation procedure, execution efficiency and execution are time-consuming, establish use-case milestone.
Further, above-mentioned automation use-case interface also includes sample parameter collection.
Further, above-mentioned use-case intersection degree includes set of uses case intersection degree and automates the intersection degree of use-case interface.
Compared with prior art, having the beneficial effect that using above-mentioned technical proposal：
1. based on service logic combination and bug Analysis and Screening sets of uses case；Tradition is reduced to sieve based on function and path analysis mode
From the complexity of example；Path coverage is lifted, reduces use-case intersection degree；
2. establishing use-case-regression test case collection-automation use-case interface multiple mapping relation, use-case reusability, lifting are improved
Build the efficiency of automatic returning, whole regression test process optimization；
3. set of uses case execution priority, classification；Control scheduling use-case implementation procedure, execution efficiency, performs time-consuming, set of uses case mileage
Upright stone tablet；Contribute to the bug of issue to find in advance, beneficial to successive ignition, reduce regression test cost, lift bug ability of discovery.
Embodiment
The present invention is described further below.
A kind of software regression testing method, specifically includes following steps：Step 1: being screened to use-case, use-case is established
Collection；Step 2: establish use-case-set of uses case-automation use-case interface multiple mapping relation；Step 3: establish set of uses case milestone；
Step 4: quantify set of uses case intersection degree and multiple mapping rate；Such as quickly smolder related to product mandate simultaneously in difference in version
Use-case, use-case intersection degree is higher, and the thinking of difference in version milestone is higher than according to milestone of quickly smoldering, will authorize related example
Focus primarily in quick smolder, related example is avoided and above intersected in difference in version, and this reduces use-case repetition
Degree, improves use-case execution efficiency.The use occured simultaneously be present in discovery path that can be as early as possible by quantizating index set of uses case intersection degree
Example, the result of bug analyses can be reflected by multiple mapping rate, improve use-case execution efficiency, complete software test.
Set of uses case intersection degree, i.e. intersection number of cases divided by the use-case of use-case set sum, it is excellent using this index as set of uses case
The standard of change, intersection degree it is lower explanation set of uses case between repeat use-case it is fewer, avoid doing retest work.Such as：Set of uses case A,
B；Include a in A, 3 use-cases of b, c include a, d, e in B, 5 use-cases of f, g, and a use-cases have path friendship in a and B in wherein A
Fork, i.e. A, B set of uses case intersections degree are 1/（3+5）, as 1/8.
Use-case multiple mapping rate, i.e., regression test case accounts for the ratio of system testing use-case, because regression test case is
As can also be used as automatic returning use-case by hand, so being multiple mapping.Regression test path coverage is used as using this index
Reference is judged, the more high then regression test case path covering of mapping rate is more.Such as：A, b, c are included in system testing use-case A,
5 test points of d, e, a is manually and automatically included in regression test case B, 3 test points of d, e, then mapping rate is 3/5.
The detailed process of the step 1 is：Step 11, according to service logic use-case is classified；Step 12, basis
Bug analysis results checking classification and the science and correctness of classification, further classify to use-case；As for modifying point
Return, first to return modifying point, secondly determine actual code modifying point, finally returning code revision influences point.According to last version
This actual code modifying point bug analyzes situation, such as pack error rate, user's attention rate, quick smoke test, difference in version, appearance
Easy side leakage and environment are time-consuming etc., filter out use-case, carry out use-case classification；Step 13, classifying further according to use-case carries out establishing use-case
Collection.
The bug analyses include analyzing the failure occurred in integration testing and system testing, also or to design side
The produced problem in face is analyzed.
The detailed process of the step 2 is：Step 21, the characteristics of being classified according to use-case, sort out related example, according to industry
Combination of features of being engaged in is into regression test case；Step 22, calculate set of uses case mapping rate；Step 23, according to set of uses case mapping rate screening,
Combine regression test case；Step 24, according to set of uses case by three layers of use-case business, use-case flow, use-case data diversity, formed from
Dynamicization use-case interface；The reserved automation use-case interface of Checkpointing, assesses the feasibility that automation is realized；Step 25, establish
Use-case-set of uses case-automation use-case interface multiple mapping relation.As modifying point set of uses case mapping rate should>90%, then it should be based on step
Regression test case mapping rate is included 90% by rapid one.
The detailed process of the step 3 is：Step 31, division set of uses case execution priority；Step 32, according to set of uses case
Execution priority, control scheduling use-case implementation procedure, execution efficiency and execution are time-consuming, establish use-case milestone.Such as at one
Use-case is performed stage by stage according to milestone in the use-case implementation procedure of team, the related bug of modifying point will be preferentially found, and
The use-case of next milestone will not be removed to perform, can so find bug in advance, the time for finding bug has been saved, be easy to as early as possible
Positioning and reparation bug.Moreover, the bug of issue has found in advance, beneficial to successive ignition, regression test cost, lifting bug hairs are reduced
Existing ability.
The automation use-case interface also includes sample parameter collection.
The use-case intersection degree includes set of uses case intersection degree and automates the intersection degree of use-case interface.
The invention is not limited in foregoing embodiment.The present invention, which expands to, any in this manual to be disclosed
New feature or any new combination, and disclose any new method or process the step of or any new combination.If this
Art personnel, it is altered or modified in the unsubstantiality that the spirit for not departing from the present invention is done, should all belongs to power of the present invention
The claimed scope of profit.
Claims (7)
- A kind of 1. software regression testing method, it is characterised in that including procedure below：Step 1: being screened to use-case, establish Set of uses case；Step 2: establish use-case-set of uses case-automation use-case interface multiple mapping relation；Step 3: establish in set of uses case Journey upright stone tablet；Step 4: quantify set of uses case intersection degree and multiple mapping rate.
- 2. software regression testing method as claimed in claim 1, it is characterised in that the detailed process of the step 1 is：Step Rapid 11, use-case classification is carried out according to service logic；Step 12, according to bug analysis results verify classification and classification science and Correctness, further carry out use-case classification；Step 13, classifying further according to use-case carries out establishing set of uses case.
- 3. software regression testing method as claimed in claim 2, it is characterised in that the bug analyses are included to integration testing Analyzed with the failure occurred in system testing, also or to the produced problem of design aspect analyzed.
- 4. software regression testing method as claimed in claim 3, it is characterised in that the detailed process of above-mentioned steps two is：Step Rapid 21, the characteristics of being classified according to use-case sorts out related example, and regression test case is combined into according to business characteristic；Step 22, Calculate set of uses case mapping rate；Step 23, according to set of uses case mapping rate screening, combination regression test case；Step 24, according to use-case Three layers of use-case business, use-case flow, use-case data diversity, formation are automated use-case interface by collection；Step 25, establish use-case-use Example collection-automation use-case interface multiple mapping relation.
- 5. software regression testing method as claimed in claim 4, it is characterised in that the automation use-case interface also includes sample This parameter set.
- 6. software regression testing method as claimed in claim 5, it is characterised in that the detailed process of the step 3 is：Step Rapid 31, set of uses case execution priority is divided；Step 32, according to set of uses case execution priority, control scheduling use-case implementation procedure, hold Line efficiency and execution are time-consuming, establish use-case milestone.
- 7. software regression testing method as claimed in claim 6, it is characterised in that the use-case intersection degree is handed over including set of uses case Fork degree and the intersection degree for automating use-case interface.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710615391.1A CN107391376A (en) | 2017-07-26 | 2017-07-26 | A kind of regression testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710615391.1A CN107391376A (en) | 2017-07-26 | 2017-07-26 | A kind of regression testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107391376A true CN107391376A (en) | 2017-11-24 |
Family
ID=60341104
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710615391.1A Pending CN107391376A (en) | 2017-07-26 | 2017-07-26 | A kind of regression testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107391376A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109344048A (en) * | 2018-08-17 | 2019-02-15 | 中国平安人寿保险股份有限公司 | A kind of test method, storage medium and server |
| CN109446097A (en) * | 2018-11-07 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of regression test case selection method, device, terminal and storage medium |
| CN110704322A (en) * | 2019-09-30 | 2020-01-17 | 上海中通吉网络技术有限公司 | Software testing method and system |
| CN110851369A (en) * | 2019-11-19 | 2020-02-28 | 泰康保险集团股份有限公司 | Policy data processing method and device |
| CN112035348A (en) * | 2020-08-26 | 2020-12-04 | 广东博智林机器人有限公司 | Automatic test platform and automatic test method thereof |
| CN112650687A (en) * | 2020-12-30 | 2021-04-13 | 绿盟科技集团股份有限公司 | Method, device, equipment and medium for testing execution priority of engine scheduling action |
| CN112783800A (en) * | 2021-03-19 | 2021-05-11 | 北京奇艺世纪科技有限公司 | Test case screening method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1877543A (en) * | 2005-06-06 | 2006-12-13 | 华为技术有限公司 | Data-driven automatic testing system and method |
| CN101329652A (en) * | 2008-07-30 | 2008-12-24 | 中兴通讯股份有限公司 | Regression test automatic system and method |
| US20140325480A1 (en) * | 2013-04-29 | 2014-10-30 | SuccessFactors | Software Regression Testing That Considers Historical Pass/Fail Events |
| CN105302720A (en) * | 2015-10-27 | 2016-02-03 | 浪潮电子信息产业股份有限公司 | Software regression test case screening method |
| CN105446885A (en) * | 2015-12-28 | 2016-03-30 | 西南大学 | Regression testing case priority ranking technology based on needs |
| CN106610891A (en) * | 2015-10-22 | 2017-05-03 | 中兴通讯股份有限公司 | Test method and device |
-
2017
- 2017-07-26 CN CN201710615391.1A patent/CN107391376A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1877543A (en) * | 2005-06-06 | 2006-12-13 | 华为技术有限公司 | Data-driven automatic testing system and method |
| CN101329652A (en) * | 2008-07-30 | 2008-12-24 | 中兴通讯股份有限公司 | Regression test automatic system and method |
| US20140325480A1 (en) * | 2013-04-29 | 2014-10-30 | SuccessFactors | Software Regression Testing That Considers Historical Pass/Fail Events |
| CN106610891A (en) * | 2015-10-22 | 2017-05-03 | 中兴通讯股份有限公司 | Test method and device |
| CN105302720A (en) * | 2015-10-27 | 2016-02-03 | 浪潮电子信息产业股份有限公司 | Software regression test case screening method |
| CN105446885A (en) * | 2015-12-28 | 2016-03-30 | 西南大学 | Regression testing case priority ranking technology based on needs |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109344048A (en) * | 2018-08-17 | 2019-02-15 | 中国平安人寿保险股份有限公司 | A kind of test method, storage medium and server |
| CN109446097A (en) * | 2018-11-07 | 2019-03-08 | 郑州云海信息技术有限公司 | A kind of regression test case selection method, device, terminal and storage medium |
| CN110704322A (en) * | 2019-09-30 | 2020-01-17 | 上海中通吉网络技术有限公司 | Software testing method and system |
| CN110704322B (en) * | 2019-09-30 | 2023-03-10 | 上海中通吉网络技术有限公司 | Software testing method and system |
| CN110851369A (en) * | 2019-11-19 | 2020-02-28 | 泰康保险集团股份有限公司 | Policy data processing method and device |
| CN112035348A (en) * | 2020-08-26 | 2020-12-04 | 广东博智林机器人有限公司 | Automatic test platform and automatic test method thereof |
| CN112650687A (en) * | 2020-12-30 | 2021-04-13 | 绿盟科技集团股份有限公司 | Method, device, equipment and medium for testing execution priority of engine scheduling action |
| CN112650687B (en) * | 2020-12-30 | 2024-03-19 | 绿盟科技集团股份有限公司 | Method, device, equipment and medium for testing execution priority of engine scheduling action |
| CN112783800A (en) * | 2021-03-19 | 2021-05-11 | 北京奇艺世纪科技有限公司 | Test case screening method and device |
| CN112783800B (en) * | 2021-03-19 | 2023-09-05 | 北京奇艺世纪科技有限公司 | Test case screening method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107391376A (en) | A kind of regression testing method | |
| CN108563556A (en) | Software defect prediction optimization method based on differential evolution algorithm | |
| CN106126413B (en) | The Software Defects Predict Methods of packaging type feature selecting based on the study of class imbalance and genetic algorithm | |
| CN104111920B (en) | A kind of Forecasting Methodology and device based on decision tree | |
| CN105574649B (en) | Tax payer tax evasion suspicion group detection method based on multi-stage MapReduce model | |
| CN105975392A (en) | Duplicated code detection method and device based on abstract syntax tree | |
| CN104881759A (en) | Business fallback integrated system based on workflow and realization method thereof | |
| CN104200842A (en) | Chip burning method and system | |
| CN107544905A (en) | The optimization method and system of regression test case collection | |
| CN109406984A (en) | The full ecological chain intelligent test analyzing method of integrated circuit | |
| CN105488089A (en) | Automatic generation method and system of quality evaluation report | |
| CN109656801B (en) | Business flow test case automatic generation system based on path adaptive technology | |
| CN108710576A (en) | Data set extending method and Software Defects Predict Methods based on isomery migration | |
| CN107967401A (en) | A kind of domain repetitive unit matching inspection method and system | |
| CN115170057A (en) | OA examination and approval control system and method based on machine learning | |
| Sanaei et al. | Systematic assessment of triticale‐based biorefinery strategies: sustainability assessment using multi‐criteria decision‐making (MCDM) | |
| CN106354631A (en) | Rapid software system regression testing method and device | |
| CN108304691A (en) | Floating agent molecular design method based on segment | |
| CN103678121A (en) | Testing case priority ordering method for embedded binary system software | |
| Murillo-Morera et al. | Software Fault Prediction: A Systematic Mapping Study. | |
| CN112765014A (en) | Automatic test system for multi-user simultaneous operation and working method | |
| CN108628873A (en) | A kind of file classification method, device and equipment | |
| CN104239212A (en) | Query method and device of test case and establishment method and device of test case | |
| CN111444106A (en) | Analysis method and system for software testable requirements | |
| CN113485940B (en) | Combined test case generation method based on parameter abstract modeling |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20171124 |