CN111813681B - Dynamic case priority ordering method and device - Google Patents

Dynamic case priority ordering method and device Download PDF

Info

Publication number
CN111813681B
CN111813681B CN202010670286.XA CN202010670286A CN111813681B CN 111813681 B CN111813681 B CN 111813681B CN 202010670286 A CN202010670286 A CN 202010670286A CN 111813681 B CN111813681 B CN 111813681B
Authority
CN
China
Prior art keywords
code
case
change
function
module
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
CN202010670286.XA
Other languages
Chinese (zh)
Other versions
CN111813681A (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.)
Industrial Securities Co ltd
Original Assignee
Industrial Securities 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 Industrial Securities Co ltd filed Critical Industrial Securities Co ltd
Priority to CN202010670286.XA priority Critical patent/CN111813681B/en
Publication of CN111813681A publication Critical patent/CN111813681A/en
Application granted granted Critical
Publication of CN111813681B publication Critical patent/CN111813681B/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/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3688Test management for test execution, e.g. scheduling of test suites
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention relates to a method and a device for sorting priorities of dynamic cases, which solve the problems of dependence on subjective consciousness of personnel and lack of objective data guidance during the current case priority sorting. To this end, the inventors provide the following: obtaining a high-frequency factor capable of representing the user access frequency based on the functional modules related to the test cases and the access amount data in the user log; identifying a use case related to code change and identifying a change code function simultaneously based on a code covering and dyeing way, thereby identifying and marking a change use case with a change risk meeting a preset standard from a use case set and obtaining a high risk factor capable of representing the change risk of the use case; and acquiring use case sequencing parameters based on the high-frequency factor and the high-risk factor acquired in the steps and a preset priority preference factor. Meanwhile, a dynamic priority ordering device for realizing the method is provided. The sorting process is based on objective data and objective operation, the priority sorting is accurate and efficient, the testing range is reduced, and the software product quality and the software testing efficiency are improved.

Description

Dynamic case priority ordering method and device
Technical Field
The invention relates to the field of computer software, in particular to a method and a device for sequencing priorities of dynamic cases.
Background
In the software development and test process, along with the increase and adjustment of software functions, testers need to continuously increase and update new test cases, so that the scale of a test case set is continuously increased, and the cost of comprehensively executing the cases is gradually increased. When the software product is updated iteratively and quickly, the full execution of the use case in a short time becomes infeasible.
In order to reduce the execution cost of the test case and improve the risk identification efficiency and capability of the test case in the software updating process, people carry out a great deal of research work aiming at the use priority of the test case, and the purpose is to discover software defects more quickly and more.
With the rapid development of the internet, use cases based on risk levels and importance levels are continuously mentioned, and software projects are concerned about the introduction control of new problems and the continuous stabilization of important functions. In the actual software development project, the priority of a test case is usually selected by combining the requirement change and the importance degree of functions, and two common practice modes are provided, wherein one mode is to determine the corresponding priority according to the newly added or adjusted functions and the important functions of the software; one is to determine case priority by predicting the risk of finding a problem according to the understanding and experience of the tester to the business. The two types of prioritization methods are more or less based on the understanding and experience of testers for services, and are not based on risk-introducing identification and analysis of importance degree of software functions, and the priorities of different testers for sequencing can be greatly different and are difficult to automate.
Disclosure of Invention
Therefore, a dynamic use case priority ranking scheme needs to be provided to solve the problems that the current use case priority ranking depends on subjective consciousness of personnel and lacks objective data guidance.
To achieve the above object, the inventor provides a dynamic case prioritization method, comprising the following steps:
acquiring a high-frequency factor capable of representing user access frequency based on the functional modules related to the test cases and the access amount data in the user log;
identifying a use case related to code change and identifying a change code function simultaneously based on a code covering and dyeing way, thereby identifying and marking a change use case with a change risk meeting a preset standard from a use case set and obtaining a high risk factor capable of representing the change risk of the use case;
and acquiring use case sequencing parameters based on the high-frequency factor and the high-risk factor acquired in the steps and a preset priority preference factor.
Further, in the method for sorting priorities of dynamic use cases, the step of "obtaining a high-frequency factor that can characterize the user access frequency based on the functional modules involved in the test cases and the access volume data in the user log" specifically includes:
obtaining logs of user access modules, counting the access amount of users to each functional module, and obtaining the access amount V of the maximum access amount module max
Marking the software function modules related to the test cases, and acquiring the access quantity of the user to the function modules related to the use cases and the access quantity V of the maximum access quantity module in the function modules case_max
The high frequency factor P capable of representing the user access frequency v Obtained according to the following formula: p v =V case_max /V max
Further, in the method for sorting priority of dynamic use cases, the step "identifying a use case related to code change based on a code overlay dyeing approach, and identifying a change code function, thereby identifying and marking a change use case whose change risk meets a preset standard from a use case set, and obtaining a high risk factor that can characterize the change risk of the use case" specifically includes:
executing the test case in an environment with a coverage rate statistic tool deployed so as to obtain a code line covered during code execution;
extracting and coloring code functions related to one or more use cases from code lines covered during the code execution;
comparing the codes before and after the change to obtain a code line of the software change;
acquiring a code change function according to the code function related to the use case and the code line of the software change;
obtaining a high risk factor D case The concrete mode is as follows: comparing the code change function with the code functions related to the use cases one by one, and if the same function exists, making D case If not, let D case =0。
Further, in the dynamic use case prioritization method, the step of "extracting and coloring code functions related to one or more use cases from a code line covered during execution of the code" specifically includes: and defining keywords according to functions of the codes, extracting the functions from the code lines, and giving corresponding values to carry out dyeing marking.
Further, in the dynamic case priority ranking method, the step "obtaining case ranking priority parameters based on the high-frequency factor and the high-risk factor obtained in the above step and the preset priority preference factor" specifically includes:
the preset priority preference factor w takes the value of an interval of [0,1 ];
use case ordering priority parameter P case Obtained according to the following formula: p is case =wD case +(1-w)P v
The inventor also provides a dynamic case priority sequencing device, which comprises a high-frequency factor acquisition unit, a high-risk factor acquisition unit and a priority parameter acquisition unit;
the high-frequency factor acquisition unit is used for acquiring a high-frequency factor capable of representing user access frequency based on the function modules related to the test cases and the access amount data in the user logs;
the high risk factor acquisition unit is used for identifying the use cases related to code change and identifying the change code function based on a code coverage dyeing way, so that the change use cases with change risks meeting the preset standard are identified and marked from the use case set, and the high risk factor capable of representing the change risks of the use cases is obtained;
the priority parameter acquiring unit is used for acquiring use case sequencing parameters based on the high-frequency factors acquired by the high-frequency factor acquiring unit, the high-risk factors acquired by the high-priority factor acquiring unit and preset priority preference factors.
Further, in the dynamic use case priority sorting apparatus, the high-frequency factor obtaining unit includes a log obtaining module, an access amount obtaining module, and a use case function marking module, where:
the log acquisition module is used for acquiring a log of the user access module;
the access amount acquisition moduleCounting the access amount of the user to each function module and obtaining the access amount V of the maximum access amount module max
The case function marking module is used for marking the software function modules related to the test cases, and then the access quantity obtaining module is also used for obtaining the access quantity of the user to the function modules related to the use cases and the access quantity V of the maximum access quantity module in the function modules according to the software function modules related to the test cases marked by the case function marking module case_max
The high-frequency factor acquisition unit acquires the high-frequency factor P capable of representing the user access frequency according to the following formula v :P v =V case_max /V max
Furthermore, in the dynamic use case priority ranking device, the high risk factor acquiring unit comprises a code line acquiring module, a code function marking module, a change code acquiring module and a code change function acquiring module;
the code line acquisition module is used for executing a test case in an environment with a coverage rate statistic tool deployed so as to acquire a code line covered during code execution;
the code function marking module is used for extracting and dyeing code functions related to one or more use cases from code lines covered during the execution of the code;
the change code acquisition module is used for comparing codes before and after change and acquiring a code line of software change;
the code change function acquisition module is used for acquiring a code change function according to the code function related to the use case and the code line of the software change;
the high risk factor acquisition unit acquires a high risk factor D capable of representing the change risk of the use case case The specific mode is as follows: comparing the code changing function with the code function related to the use case one by one, and if the same function exists, ordering D case 1, otherwise, let D case =0。
Further, in the dynamic use case prioritization apparatus, the code function marking module "extracting and coloring the code function involved in marking one or more use cases from the code line covered during the execution of the code" specifically includes: and defining keywords according to functions of the codes, extracting the functions from the code lines, and giving corresponding values to carry out dyeing marking.
Furthermore, in the dynamic use case priority ranking device, the priority parameter obtaining unit obtains the use case ranking priority parameter P case The method specifically comprises the following steps:
the preset priority preference factor w takes the value of an interval of [0,1 ];
P case obtained according to the following formula: p case =wD case +(1-w)P v
Different from the prior art, the method disclosed by the invention reversely identifies the use cases related to code change by using a use case-to-code overlay dyeing technology, and identifies the change code function by using a code management diff tool, so that the changed high-risk use cases are identified from a large number of use case sets. And determining a corresponding sign through the use case and software function module, and mapping the high-frequency use case used by the user by combining the user behavior statistical log on the software function. And weighting and adding the high-risk and high-frequency use cases, and automatically identifying and obtaining the priority sequence of the use cases. The technical scheme has the following advantages:
firstly, the priority ranking of the use cases is an important method for improving the test quality and the test efficiency in the software project test. The priority ranking of the use cases in the current practice depends on the experience of testers and the understanding of software services, and is difficult to be specifically quantized or automated. The technology of the patent provides a feasible sustainable practice method for dynamically calculating the priority of the use cases through data, the dependence on the capability of testers is separated, and automatic sequencing and batch sequencing of the use cases can be realized through a tool mode.
Secondly, the patent accords with the principle of sequencing the use case priority for most software project development based on the risk introduction and the access amount. The sorting process is based on objective data and objective operation, the priority sorting is more accurate and efficient, the testing range is narrowed, and the software product quality and the software testing efficiency are improved.
In addition, the method can be used as an auxiliary mode for accurately testing the software project based on the case priority sequence of code change. The method can be used for assisting in the formulation and implementation of a test scheme; the test case effectiveness is improved in an auxiliary mode; the low-contribution-degree use cases are eliminated in an auxiliary mode, and the effective reuse rate of the use cases is improved; development assistance, test problem reproduction and positioning.
Drawings
FIG. 1 is a flowchart illustrating a method for dynamic case prioritization according to an embodiment;
fig. 2 is a block diagram of a dynamic use case prioritization apparatus according to this embodiment.
Description of reference numerals:
1-a high frequency factor acquisition unit;
11-a log acquisition module; 12-an access quantity acquisition module; 13 use case function marking module
2-a high risk factor acquisition unit;
21-code line acquisition module; 22-code function marking module; 23-change code acquisition module;
24-code change function acquisition module
3-priority parameter acquisition unit.
Detailed Description
To explain technical contents, structural features, and objects and effects of the technical solutions in detail, the following detailed description is given with reference to the accompanying drawings in conjunction with the embodiments.
Referring to fig. 1, the present embodiment provides a method for dynamically sorting priorities of use cases, which includes the following steps:
s1, acquiring a high-frequency factor capable of representing user access frequency based on the function modules related to the test cases and the access amount data in the user log;
s2, identifying the use cases related to code change based on the code covering and dyeing way, and identifying the change code function, thereby identifying and marking the change use cases with change risks meeting the preset standard from the use case set, and obtaining high risk factors capable of representing the change risks of the use cases;
and S3, acquiring use case sequencing parameters based on the high-frequency factor and the high-risk factor acquired in the above steps and a preset priority preference factor.
Further, step S1 includes the following sub-steps:
s11, obtaining the log of user access module, counting the access volume of user to each function module, obtaining the access volume V of the maximum access volume module max (ii) a For example, there are n functional modules in total, and the access amount of each module is: v mod1 ,V mon2 ,…,V modn And order V max The largest one among them.
S12, marking the software function modules related to the test case, obtaining the access quantity of the user to the function modules related to the use case and the access quantity V of the maximum access quantity module case_max (ii) a That is, V acquired in step S11 mod1 ,V mon2 ,…,V modn In the corresponding functional modules, a plurality of functional modules are related to the test case (m is set, obviously m is less than or equal to n), and the access number V of the functional modules related to the test case is selected case_mod1 ,V case_mod2 ,…,V case_modm And let V be the maximum one case_max
S13, high frequency factor P capable of characterizing user access frequency v Obtained according to the following formula: p v =V case_max /V max
Further, step S2 includes the following sub-steps:
s21, executing the test case in the environment with the coverage rate statistic tool deployed, thereby obtaining the code line covered during the code execution;
s22, extracting and dyeing code functions related to one or more use cases from code lines covered in the code execution; specifically, keywords are defined according to functions of the codes, the functions are extracted from code lines, and corresponding values are given for dyeing and marking.
S23, comparing the codes before and after the change to obtain a code line of the software change;
s24, acquiring a code change function according to the code function related to the use case and the code line of the software change;
s25, obtaining a high risk factor D case The concrete mode is as follows: comparing the code changing function with the code function related to the use case one by one, and if the same function exists, ordering D case If not, let D case =0。
Further, the manner of acquiring the use case sorting priority parameter in step S3 specifically includes: the preset priority preference factor w takes the value of [0, 1%]An interval; use case ordering priority parameter P case Obtained according to the following formula: p case =wD case +(1-w)P v . Wherein the parameter w takes the value [0, 1%]The interval represents the use case priority acquisition preference, the closer to 0, the more important risk introduction of the use case sequence is represented, and the closer to 1, the more important function importance of the use case sequence is represented, which is a parameter that can be determined by a concrete implementation operator.
The inventor also provides a dynamic case priority sequencing device, which comprises a high-frequency factor acquisition unit 1, a high-risk factor acquisition unit 2 and a priority parameter acquisition unit 3;
the high-frequency factor obtaining unit 1 is used for obtaining a high-frequency factor capable of representing user access frequency based on the function modules related to the test cases and the access amount data in the user logs;
the high risk factor acquiring unit 2 is used for identifying the use cases related to code change and identifying the change code function based on the code coverage dyeing way, so as to identify and mark the change use cases with change risks meeting the preset standard from the use case set and acquire the high risk factor capable of representing the change risks of the use cases;
the priority parameter acquiring unit 3 is configured to acquire the use case sorting parameters based on the high-frequency factor acquired by the high-frequency factor acquiring unit 1, the high-risk factor acquired by the high-priority factor acquiring unit 2, and the preset priority preference factor.
Further, in the dynamic use case prioritization apparatus, the high-frequency factor obtaining unit 1 includes a log obtaining module 11, an access amount obtaining module 12, and a use case function marking module 13, where:
the log obtaining module 11 is configured to obtain a log of a user access module;
the access quantity obtaining module 12 is used for counting the access quantity of the user to each functional module, and obtaining the access quantity V of the maximum access quantity module max (ii) a For example, there are n functional modules in total, and the access amount of each module is: v mod1 ,V mon2 ,…,V modn And order V max The largest one among them.
The use case function marking module 13 is used for marking the software function modules related to the test use cases, and then the access amount obtaining module 12 is further used for obtaining the access amount of the user to the function modules related to the use cases and the access amount V of the maximum access amount module in the access amount according to the software function modules related to the test use cases marked by the use case function marking module 13 case_max (ii) a That is, V acquired by the access amount acquisition module 12 before mod1 ,V mon2 ,…,V modn In the corresponding functional modules, a plurality of functional modules are related to the test case (m is set, obviously m is less than or equal to n), and the access number V of the functional modules related to the test case is selected case_mod1 ,V case_mod2 ,…,V case_modm And let V be the maximum one case_max
The high frequency factor obtaining unit 1 obtains the high frequency factor P capable of representing the user access frequency according to the following formula v :P v =V case_max /V max
Further, in the dynamic use case priority ranking device, the high risk factor obtaining unit 2 includes a code line obtaining module 21, a code function marking module 22, a change code obtaining module 23, and a code change function obtaining module 24;
the code line obtaining module 21 is configured to execute the test case in an environment where a coverage statistics tool is deployed, so as to obtain a code line covered by the code when executing;
the code function marking module 22 is configured to extract and color a code function related to one or more use cases from a code line covered during execution of the code, and specifically includes: and defining keywords according to functions of the codes, extracting the functions from the code lines, and giving corresponding values to carry out dyeing marking.
The change code obtaining module 23 is configured to compare codes before and after the change, and obtain a code line of the software change;
the code change function 24 obtaining module is used for obtaining a code change function according to a code function related to a use case and a code line of software change;
the high risk factor acquiring unit 2 acquires a high risk factor D which can represent the change risk of the use case case The specific mode is as follows: comparing the code changing function with the code function related to the use case one by one, and if the same function exists, ordering D case If not, let D case =0。
Further, the priority parameter acquiring unit 3 acquires a use case sorting priority parameter P case The method specifically comprises the following steps:
the preset priority preference factor w takes the value of [0, 1%]An interval; p case Obtained according to the following formula: p case =wD case +(1-w)P v . Wherein the parameter w takes the value [0, 1%]The interval represents the use case priority acquisition preference, the closer to 0, the more important risk introduction of the use case sequence is represented, and the closer to 1, the more important function importance of the use case sequence is represented, which is a parameter that can be determined by a concrete implementation operator.
Different from the prior art, the method disclosed by the invention reversely identifies the use cases related to code change by using a use case-to-code covering and dyeing technology, and identifies the change code function by adopting a code management diff tool, so that the changed high-risk use cases are identified from a large number of use cases in a centralized manner. And determining a corresponding mark through the use case and software function module, and mapping the high-frequency use case used by the user by combining the user behavior statistical log on the software function. And weighting the high-risk and high-frequency cases, adding the high-risk and high-frequency cases, and automatically identifying and acquiring the priority sequence of the cases. The technical scheme has the following advantages:
firstly, the priority ranking of the use cases is an important method for improving the test quality and the test efficiency in the software project test. The priority ranking of the use cases in the current practice depends on the experience of testers and the understanding of software services, and is difficult to be specifically quantized or automated. The technology of the patent provides a feasible sustainable practical method for dynamically calculating the case priority through data, the dependence of the capability of testers is separated, and automatic sequencing and batch sequencing of the cases can be realized in a tool mode.
Secondly, the patent accords with the principle of sequencing the use case priority for most software project development based on the risk introduction and the access amount. The sorting process is based on objective data and objective operation, the priority sorting is more accurate and efficient, the testing range is narrowed, and the software product quality and the software testing efficiency are improved.
In addition, the method can be used as an auxiliary mode for accurately testing the software project based on the case priority sequence of code change. The method can be used for assisting in the formulation and implementation of a test scheme; the test case effectiveness is improved in an auxiliary mode; the low-contribution-degree use cases are eliminated in an auxiliary mode, and the effective reuse rate of the use cases is improved; auxiliary development, test problem reproduction and positioning.
It should be noted that, although the above embodiments have been described herein, the invention is not limited thereto. Therefore, based on the innovative concepts of the present invention, the technical solutions of the present invention can be directly or indirectly applied to other related technical fields by making changes and modifications to the embodiments described herein, or by using equivalent structures or equivalent processes performed in the content of the present specification and the attached drawings, which are included in the scope of the present invention.

Claims (4)

1. A dynamic use case priority ordering method is characterized by comprising the following steps:
acquiring a high-frequency factor capable of representing user access frequency based on the functional modules related to the test cases and the access amount data in the user log;
identifying a use case related to code change and identifying a change code function simultaneously based on a code covering and dyeing way, thereby identifying and marking a change use case with a change risk meeting a preset standard from a use case set and obtaining a high risk factor capable of representing the change risk of the use case;
the step of obtaining a high-frequency factor capable of representing the user access frequency based on the functional modules related to the test cases and the access amount data in the user log specifically comprises the following steps: obtaining logs of user access modules, counting the access amount of users to each functional module, and obtaining the access amount V of the maximum access amount module max (ii) a Marking the software function modules related to the test cases, and acquiring the access quantity of the user to the function modules related to the use cases and the access quantity V of the maximum access quantity module in the function modules case_max (ii) a The high frequency factor P capable of representing the user access frequency v Obtained according to the following formula: p v =V case_max /V max (ii) a The step of identifying the use cases related to code change and identifying the change code function based on a code coverage dyeing way, thereby identifying and marking the change use cases with change risks meeting the preset standard from the use case set and obtaining high risk factors capable of representing the change risks of the use cases specifically comprises the following steps: executing the test case in an environment with a coverage rate statistic tool deployed so as to obtain a code line covered during code execution; extracting and coloring code functions related to one or more use cases from code lines covered during the execution of the code; comparing the codes before and after the change to obtain a code line of the software change; acquiring a code change function according to the code function related to the use case and the code line of the software change; obtaining high risk factor D case The concrete method is as follows: comparing the code changing function with the code function related to the use case one by one, and if the same function exists, ordering D case If not, let D case =0;
Based on the high-frequency factor and the high-risk factor obtained in the above steps and the preset priority preference factor, obtaining a use case sequencing parameter, specifically including: the preset priority preference factor w takes the value of [0, 1%]An interval; use case ordering priority parameter P case Obtained according to the following formula: p case =wD case +(1-w)P v
2. The dynamic use case prioritization method of claim 1, wherein the step of "extracting and coloring code functions involved in marking one or more use cases from a code line covered in execution of the code" specifically comprises: and defining keywords according to the functions of the codes, extracting the functions from the code lines, and endowing corresponding values for dyeing marking.
3. A dynamic use case priority sequencing device is characterized by comprising a high-frequency factor acquisition unit, a high-risk factor acquisition unit and a priority parameter acquisition unit;
the high-frequency factor acquisition unit is used for acquiring a high-frequency factor capable of representing user access frequency based on the function modules related to the test cases and the access amount data in the user logs; the high-frequency factor acquisition unit comprises a log acquisition module, an access quantity acquisition module and a use case function marking module, wherein: the log acquisition module is used for acquiring a log of the user access module; the access quantity acquisition module is used for counting the access quantity of the user to each functional module and acquiring the access quantity V of the maximum access quantity module max (ii) a The case function marking module is used for marking the software function modules related to the test cases, and then the access quantity obtaining module is also used for obtaining the access quantity of the user to the function modules related to the use cases and the access quantity V of the maximum access quantity module in the function modules according to the software function modules related to the test cases marked by the case function marking module case_max (ii) a The high-frequency factor acquisition unit acquires the high-frequency factor P capable of representing the user access frequency according to the following formula v :P v =V case_max /V max
The high risk factor acquisition unit is used for identifying use cases related to code change and identifying a change code function based on a code coverage dyeing way, so that change use cases with change risks meeting a preset standard are identified and marked from a use case set, and high risk factors capable of representing the change risks of the use cases are acquired; the high risk factor acquisition unit comprises a code line acquisition module, a code function marking module, a change code acquisition module and a code change function acquisition module; the code line acquisition module is used for executing a test case in an environment with a coverage rate statistical tool deployed so as to acquire a code line covered during code execution; the code function marking module is used for extracting and dyeing and marking one or more code functions related to one or more use cases from a code line covered during the code execution; the change code acquisition module is used for comparing codes before and after change and acquiring a code line of software change; the code change function acquisition module is used for acquiring a code change function according to a code function related to a use case and a code line of software change;
the high risk factor acquisition unit acquires a high risk factor D capable of representing the change risk of the use case case The specific mode is as follows: comparing the code changing function with the code function related to the use case one by one, and if the same function exists, ordering D case 1, otherwise, let D case =0;
The priority parameter acquiring unit is used for acquiring use case sequencing parameters based on the high-frequency factors acquired by the high-frequency factor acquiring unit, the high-risk factors acquired by the high-priority factor acquiring unit and preset priority preference factors; the priority parameter acquiring unit acquires a case sorting priority parameter P case The method specifically comprises the following steps: the preset priority preference factor w takes the value of [0, 1%]An interval; p case Obtained according to the following formula: p is case =wD case +(1-w)P v
4. The dynamic use case prioritization apparatus according to claim 3, wherein the code function marking module "extracting and coloring code functions involved in marking one or more use cases from a code line covered during execution of the code" specifically includes: and defining keywords according to functions of the codes, extracting the functions from the code lines, and giving corresponding values to carry out dyeing marking.
CN202010670286.XA 2020-07-13 2020-07-13 Dynamic case priority ordering method and device Active CN111813681B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010670286.XA CN111813681B (en) 2020-07-13 2020-07-13 Dynamic case priority ordering method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010670286.XA CN111813681B (en) 2020-07-13 2020-07-13 Dynamic case priority ordering method and device

Publications (2)

Publication Number Publication Date
CN111813681A CN111813681A (en) 2020-10-23
CN111813681B true CN111813681B (en) 2022-09-09

Family

ID=72842313

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010670286.XA Active CN111813681B (en) 2020-07-13 2020-07-13 Dynamic case priority ordering method and device

Country Status (1)

Country Link
CN (1) CN111813681B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115422095A (en) * 2022-11-07 2022-12-02 易方信息科技股份有限公司 Regression test case recommendation method, device, equipment and medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107835982A (en) * 2015-05-04 2018-03-23 赛义德·卡姆兰·哈桑 Method and apparatus for management security in a computer network
CN110109820A (en) * 2019-03-19 2019-08-09 深圳壹账通智能科技有限公司 Regression test case determines method, apparatus, computer equipment and storage medium
CN110134588A (en) * 2019-04-16 2019-08-16 江苏大学 A kind of priorities of test cases sort method and test macro based on code and combined covering
US10430319B1 (en) * 2018-05-04 2019-10-01 Fmr Llc Systems and methods for automatic software testing
CN110825621A (en) * 2019-10-16 2020-02-21 四川大学 Regression test case priority calculation method based on dynamic risk

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107835982A (en) * 2015-05-04 2018-03-23 赛义德·卡姆兰·哈桑 Method and apparatus for management security in a computer network
US10430319B1 (en) * 2018-05-04 2019-10-01 Fmr Llc Systems and methods for automatic software testing
CN110109820A (en) * 2019-03-19 2019-08-09 深圳壹账通智能科技有限公司 Regression test case determines method, apparatus, computer equipment and storage medium
CN110134588A (en) * 2019-04-16 2019-08-16 江苏大学 A kind of priorities of test cases sort method and test macro based on code and combined covering
CN110825621A (en) * 2019-10-16 2020-02-21 四川大学 Regression test case priority calculation method based on dynamic risk

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
《一种动态约简的多目标测试用例优先级排序方法》;张娜;《计算机科学》;20200111;第46卷(第12期);208-212 *
《基于风险分析的回归测试用例优先级排》;于海;《计算机学报》;20191107;第42卷(第10期);2127-2144 *

Also Published As

Publication number Publication date
CN111813681A (en) 2020-10-23

Similar Documents

Publication Publication Date Title
CN108255730B (en) Software interface testing method, testing equipment, storage medium and device
CN110264274B (en) Guest group dividing method, model generating method, device, equipment and storage medium
CN106888060B (en) Anti-interference test method and system for wireless communication module
CN111475417A (en) Automatic testing method, device, equipment and storage medium
CN111813681B (en) Dynamic case priority ordering method and device
CN111290967A (en) Software defect prediction method, device, equipment and storage medium
CN115393645B (en) Automatic soil classification and naming method, system, storage medium and intelligent terminal
CN114971433B (en) Quality control method, device, equipment and storage medium based on industrial internet
CN109523188A (en) The warship person's cognitive features work efficiency assessment method and system shown towards man-machine interface
CN105487970A (en) Interface display method and apparatus
CN114971693A (en) Engineering cost consultation management system based on BIM
WO2019196107A1 (en) Method for detecting composition of substance, related device, and computer readable storage medium
CN113312261A (en) Test case screening method, test case screening equipment, storage medium and device
CN110162361B (en) Intelligent prompting method and device based on user behavior, terminal and storage medium
CN114693554B (en) Big data image processing method and system
CN111537447A (en) Spectrum reconstruction method, printing quality evaluation method and system and electronic equipment
CN114238110A (en) Software application testing method, device, equipment and storage medium
CN113420686A (en) Power transmission line inspection method, device and system
CN115277487B (en) Communication processing system of electronic terminal
CN111881008A (en) Data evaluation method, data evaluation device, model training method, model evaluation device, model training equipment and storage medium
CN110908889A (en) Automatic testing method and device and control equipment
CN112734767B (en) Extraction method, device, equipment and medium based on pathological image tissue region
CN110443379A (en) Data processing method, device and server
CN115647615B (en) Module driving method, device and equipment of laser cutter and storage medium
CN115375854B (en) Ultrasonic image equipment image processing method fused with liquid crystal device and related device

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