CN109062794A - A kind of the determination method, apparatus and electronic equipment of software evaluating result - Google Patents
A kind of the determination method, apparatus and electronic equipment of software evaluating result Download PDFInfo
- Publication number
- CN109062794A CN109062794A CN201810816785.8A CN201810816785A CN109062794A CN 109062794 A CN109062794 A CN 109062794A CN 201810816785 A CN201810816785 A CN 201810816785A CN 109062794 A CN109062794 A CN 109062794A
- Authority
- CN
- China
- Prior art keywords
- test
- case
- bug
- test case
- attributive character
- 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.)
- Granted
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
-
- 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/3692—Test management for test results analysis
Abstract
The embodiment of the invention provides a kind of determination methods of software evaluating result, device and electronic equipment, scheme is as follows: available to carry out testing required multiple test cases for software under testing, for each test case, each attributive character based on the test, it is determined to indicate the use-case number of each attributive character of the test case, acquisition carries out software under testing using the test case to test generated bug, as the corresponding test bug of the test case, for each test bug of generation, the use-case for being corresponding with the test case of test bug is numbered and is associated with test bug, obtain the incidence relation between test bug and use-case number, based on incidence relation, determine the evaluating result of software under testing.Using scheme provided in an embodiment of the present invention, the efficiency of software assessment can be improved convenient for determining the evaluating result of software under testing according to the incidence relation between test bug and use-case number.
Description
Technical field
The present invention relates to software testing technology fields, more particularly to a kind of determination method, apparatus of software evaluating result
And electronic equipment.
Background technique
Software test is the important component in software development process, and developer requires to build software according to exploitation
Software section in system or system.In software development process, developer often develops a version, and tester needs
The version currently developed is tested, and software evaluation is made according to test result, later, tester can survey software
Result is commented to be submitted in bug management system.Developer according to the assessment problem reflected in bug management system to current version into
Row optimization, design bring out a new edition, then carry out software assessment by tester, to form a benign cycle, are finally reached
Exploitation requires.
However, during the test, the test of each version be completed jointly by several testers, meanwhile,
Each version includes multiple functional modules, and tester needs to go out for different function module designs corresponding test and uses
Example, tests version according to test case.During the test, with the continuous iteration of version, the quantity of test case
It is more and more, test each time generation bug (loophole) often have it is hundreds of, it might even be possible to reach thousands of.
In general, in entire test process, current version is surveyed according to test case by tester first
Examination, can generate corresponding bug, the bug that then tester can generate each test case is attached to corresponding survey after test
Behind example on probation, test case and bug are associated with this, the test case that tester can count all later is produced with it
Raw bug will generate the test case more than bug and function problem etc. of its reflection, as the foundation of software evaluation, according to
Software evaluating result is finally submitted bug management system for developer's ginseng current version software evaluation by the foundation again
It examines.
It can be seen that tester needs for test case and bug to be associated in software assessment process, and statistics
The problem of bug reflects requires a great deal of time, and causes software assessment efficiency relatively low.
Summary of the invention
The determination method, apparatus and electronic equipment for being designed to provide a kind of software evaluating result of the embodiment of the present invention,
To realize the efficiency for improving software assessment.Specific technical solution is as follows:
The embodiment of the invention provides a kind of determination method of software evaluating result, the methods, comprising:
It obtains and carries out testing required multiple test cases for software under testing；
For each test case, each attributive character based on the test case is determined to indicate that the test is used
The use-case number of each attributive character of example；
For each test case, obtain caused by being tested using the test case to the software under testing
Bug, as the corresponding test bug of the test case；
For each test bug of generation, it will be corresponding with the use-case number of the test case of test bug, with the test
Bug is associated, and obtains the incidence relation between test bug and use-case number；
Based on the incidence relation, the evaluating result of the software under testing is determined.
Further, each attributive character based on the test case is determined to indicate that each attribute of the test case is special
The use-case of sign is numbered, comprising:
Obtain the characteristic ID of each attributive character of the test case and unique initial ID of the test case；
Generation includes that the characteristic ID of each attributive character of the test case and the use-case of unique initial ID are numbered,
Use-case as the test case is numbered.
Further, the method, further includes:
For each test case, according to the test case to the characteristic ID in application examples number, statistics has
The test case of same characteristic features ID, as similar test case；
When the quantity of the similar test case is greater than preset use-case quantity, used for similar test described in each
Example redefines the use-case number of the test case by increasing the test case to the attributive character in application examples number.
Further, each attributive character includes at least one of following attributive character:
Scene characteristic, functional character and operation behavior feature when the software under testing is tested.
Further, for each test bug of generation, it will be corresponding with the use-case number of the test case of test bug,
It is associated with test bug, obtains the incidence relation between test bug and use-case number, comprising:
For each test bug that test generates, the use-case number of the test case of test bug, label will be corresponding with
In test bug, the incidence relation between test bug and use-case number is indicated with the use-case number marked in test bug.
Further, it is based on the incidence relation, determines the evaluating result of the software under testing, comprising:
It based on the incidence relation, is numbered according to the use-case marked in the test bug, each attribute in statistics use-case number
The number that feature occurs；
Compare whether the number that each attributive character occurs is greater than preset threshold value；
According to the result of the comparison and each attributive character numbers associated test bug to application examples, determines described to be measured soft
Test result, Measurement results and the comments of part, as evaluating result.
Further, the method, further includes:
It obtains according to the comments in the evaluating result, the test case is increased, deleted or modified
The test case obtained afterwards, as testing required test case next time.
The embodiment of the invention provides a kind of determining device of software evaluating result, described devices, comprising:
Test case obtains module, carries out testing required multiple test cases for software under testing for obtaining；
Use-case number determining module is used for for each test case, each attributive character based on the test case,
It is determined to indicate the use-case number of each attributive character of the test case；
It tests bug and obtains module, for being directed to each test case, obtain using the test case to described to be measured
Software carries out testing generated bug, as the corresponding test bug of the test case；
Incidence relation determining module, for for each test bug generated, the test for being corresponding with test bug to be used
The use-case number of example, is associated with test bug, obtains the incidence relation between test bug and use-case number；
Evaluating result determining module determines the evaluating result of the software under testing for being based on the incidence relation.
Further, use-case number determining module, comprising:
ID acquisition submodule, for obtaining the characteristic ID and the test case of each attributive character of the test case
Unique initial ID；
Use-case number generate submodule, for generate include the test case each attributive character characteristic ID and institute
The use-case number of unique initial ID is stated, the use-case as the test case is numbered.
Further, described device, further includes:
Similar test case statistical module compiles application examples according to the test case for being directed to each test case
The characteristic ID in number counts the test case with same characteristic features ID, as similar test case；
Use-case number redefines module, is greater than preset use-case quantity for the quantity when the similar test case
When, for similar test case described in each, by increasing the test case to the attributive character in application examples number, again
Determine the use-case number of the test case.
Further, each attributive character includes at least one of following attributive character:
Scene characteristic, functional character and operation behavior feature when the software under testing is tested.
Further, incidence relation determining module will be corresponding with specifically for each test bug generated for test
The use-case of the test case of test bug is numbered, and is marked in test bug, with the use-case number table marked in test bug
Show the incidence relation between test bug and use-case number.
Further, evaluating result determining module, comprising:
Number statistic submodule is numbered for being based on the incidence relation according to the use-case marked in the test bug,
Count the number that each attributive character occurs in use-case number；
Whether Comparative sub-module, the number occurred for each attributive character are greater than preset threshold value；
Evaluating result determines submodule, is used for according to the result of the comparison and each attributive character is associated to application examples number
Bug is tested, the test result, Measurement results and comments of the software under testing are determined, as evaluating result.
Further, described device, further includes:
Test case reacquires module, for obtaining according to the comments in the evaluating result, to the test
The test case that use-case obtains after being increased, deleted or being modified, as testing required test case next time.
The embodiment of the invention also provides a kind of electronic equipment, the electronic equipment includes processor, communication interface, storage
Device and communication bus, wherein processor, communication interface, memory complete mutual communication by communication bus；
Memory, for storing computer program；
Processor when for executing the program stored on memory, realizes the determination of any of the above-described software evaluating result
Method and step.
The embodiment of the invention also provides a kind of computer readable storage medium, the computer readable storage medium memory
Computer program is contained, the computer program realizes the determination method of any of the above-described software evaluating result when being executed by processor
The step of.
The determination method, apparatus and electronic equipment of a kind of software evaluating result provided in an embodiment of the present invention, it is available
It carries out testing required multiple test cases for software under testing, for each test case, each attribute based on the test is special
Sign is determined to indicate that the use-case number of each attributive character of the test case obtains for each test case and uses the survey
Example on probation carries out software under testing to test generated bug, as the corresponding test bug of the test case, for the every of generation
The use-case for being corresponding with the test case of test bug is numbered and is associated with test bug, tested by a test bug
Incidence relation between bug and use-case number, is based on incidence relation, determines the evaluating result of software under testing.Pass through the above method
Software can be improved convenient for determining the evaluating result of software under testing according to the incidence relation between test bug and use-case number
The efficiency of assessment.
Certainly, implement any of the products of the present invention or method it is not absolutely required at the same reach all the above excellent
Point.
Detailed description of the invention
In order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, to embodiment or will show below
There is attached drawing needed in technical description to be briefly described.
Fig. 1 is a kind of one of flow chart of the determination method of software evaluating result provided in an embodiment of the present invention；
Fig. 2 is a kind of structural schematic diagram of case management system provided in an embodiment of the present invention；
Fig. 3 is the two of a kind of flow chart of the determination method of software test result provided in an embodiment of the present invention；
Fig. 4 is the apparatus structure schematic diagram that a kind of software evaluating result provided in an embodiment of the present invention determines；
Fig. 5 is the structural schematic diagram of a kind of electronic equipment provided in an embodiment of the present invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention is described.
The determination method, apparatus and electronic equipment of a kind of software evaluating result provided in an embodiment of the present invention, it is available
It carries out testing required multiple test cases for software under testing, for each test case, each attribute based on the test is special
Sign is determined to indicate that the use-case number of each attributive character of the test case obtains for each test case and uses the survey
Example on probation carries out software under testing to test generated bug, as the corresponding test bug of the test case, for the every of generation
The use-case for being corresponding with the test case of test bug is numbered and is associated with test bug, tested by a test bug
Incidence relation between bug and use-case number, is based on incidence relation, determines the evaluating result of software under testing.Pass through the above method
Software can be improved convenient for determining the evaluating result of software under testing according to the incidence relation between test bug and use-case number
The efficiency of assessment.
The embodiment of the invention provides a kind of determination methods of software evaluating result, as shown in Figure 1, may include following step
It is rapid:
Step S101 is obtained and is carried out testing required multiple test cases for software under testing.
In this step, the full dose that test case can be corresponded to from software under testing is concentrated, and is obtained needed for software under testing test
Multiple test cases.
Step S102, for each test case, each attributive character based on the test case is determined to indicate the survey
The use-case number of each attributive character of example on probation.
In this step, it can be directed to each test case acquired in step s101, obtain each category of the test case
Property the characteristic ID of feature and unique initial ID of the test case, according to characteristic ID and unique initial ID, generation includes this
The use-case number of the characteristic ID of each attributive character of test case and unique initial ID, the use-case as the test case are compiled
Number.Wherein, each attributive character includes at least one of following feature: scene characteristic when software under testing is tested, functional character and behaviour
Make behavioural characteristic.
Specifically, being directed to each test case, corresponding use-case number can be indicated are as follows:
xx_yy_zz_id
Wherein, the characteristic ID of each characteristic attribute of xx, yy and zz test case, id indicate the unique of the test case
Initial ID.
For example, the use-case number of a certain test case can indicate are as follows:
H264_HCDN_Seek_10
H264 indicates that the corresponding test scene of the test case is H264 player, and HCDN indicates that the test case is corresponding
Test function is to test the HCDN function of software under testing, and Seek indicates the corresponding concrete operations behavior of the test case, and 10 indicate
Unique initial ID of the test case.
In embodiments of the present invention, each attributive character in above-mentioned each test case corresponding use-case number, in addition to
Scene characteristic when software test, functional character and operation behavior feature are surveyed, prerequisite when can also include test, it is contemplated that
Effect, remark information, it might even be possible to a variety of attributive character such as name including tester.It manages for convenience simultaneously, it can be with
According to preset sequence, the use-case number of the test case is generated.Wherein, preset sequence can be according to the test case
Different characteristic attribute arranges above-mentioned each attributive character according to progressive relationship, for example, the use-case number of a certain test case can
To be, software under testing uses the test scene when testing case _ for function of the test under the test scene _ to be directed to
The concrete operations behavior of the test function _ for the operation behavior test before prerequisite _ it is pre- under the prerequisite
Phase effect _ id.It is illustrated by taking above-mentioned use-case number H264_HCDN_Seek_10 as an example, use-case number can indicate the survey
Example on probation is used in the test environment of H264, for the HCDN function of software under testing, carries out lookup test, and is searched specific
Content can be supplemented as the case may be.
Further, it is numbered for the use-case of above-mentioned each test case, for the management convenient for being numbered to use-case, Ke Yi
When each use-case number generates, the quantity of each characteristic attribute in use-case number is controlled.For example, being used for each test
Example, all using its all attributive character as the characteristic ID in the use-case of test case number, although can be complete, accurate
State out all properties feature of the test case, the excessively redundancy but use-case number will seem.It is therefore possible to use with lower section
Method is controlled the attributive character in use-case number.Specific embodiment may is that
For each test case, according to the test case to the characteristic ID in application examples number, statistics has identical
The test case of characteristic ID, as similar test case.
When the quantity of similar test case is greater than preset use-case quantity, for each similar test case, pass through
Increase the test case to the attributive character in application examples number, redefines the use-case number of the test case.
Specifically, assuming that an existing software under testing needs to verify it in the operating system of Linux class, the software is verified
User's login function, it is assumed that the test case for including in the login function includes the test case 25 of account login authentication again
It is a, the test case of no account login authentication 5, wherein have in the test case of account login authentication includes that account inputs again
The test case of correct verification 7, test case 18 of account input error verifying.
Accordingly, it is assumed that preset use-case quantity is 20, in the use-case number for determining above-mentioned 30 test cases
When, use-case number can be, e.g., 30 use-cases of Linux_ login _ such form of id number, because of this 30 use-case numbers
Characteristic ID it is identical, therefore, it is similar test case that this 30 test cases, which number corresponding test case,.Due to similar
The quantity 30 of test case is greater than preset use-case quantity 20, therefore, it is special can to increase new attribute in above-mentioned use-case number
Sign redefines the use-case number of 30 test cases.For example, 5 test cases for no account login authentication can be with table
It is shown as: Linux_ login _ without account _ id, similarly, for 25 test cases for having account login authentication, since its quantity is big
In preset use-case quantity, therefore, this 25 test cases corresponding use-case number can be indicated are as follows: Linux_ logs in _ there is account
Number _ account inputs correct _ id and Linux_ are logged in _ account _ account input error _ two kinds of id form.
In embodiments of the present invention, for convenience of the management to above-mentioned test case, use-case can be constituted using tree structure
Management system, for being managed to test case.As shown in Fig. 2, each father node indicates in the case management system
The use-case module of attributive character is corresponded to, the connection relationship between these use-case modules is referred to each attribute in above-mentioned use-case number
The sequence of feature successively generates.For each branch in the tree structure, storage has pair in the bottom child node of the branch
The test case for the attributive character answered, each attributive character that test case indicates the characteristic ID in application examples number, in sequence
Use-case module in the upper and branch corresponds.It, can be by Linux use-case module by taking the test of above-mentioned user's login function as an example
As father node, child node includes to log in test case module；To log in test case module as father node, child node packet
Test case module is logged in containing no account, has account to log in test case module, wherein no account logs in test case module
Include, e.g., Linux_ logs in _ and the test case of use-case without the such form of account _ id number shares 5, and to there is account
Login test case module is father node, and child node includes that account inputs correct test case module and account input error survey
Example module on probation, wherein account inputs correct test case module and includes, and e.g., Linux_ logs in _ have account _ account input
Test case totally 7 of the use-case number of the such form of correctly _ id, account input error test case module includes, e.g.,
Linux_ logs in _ has test case totally 18 of account _ account input error _ id such form use-case number.
In embodiments of the present invention, it for the determination method of above-mentioned unique initial ID, can be directly used in step S101
The ID number for the full dose integrated test use-case mentioned is numbered as unique initial ID；Alternatively, according to foregoing description, in above-mentioned use-case
In management system because the quantity of similar test case be it is certain, can be directly according to the number of similar test case quantity
It is numbered, each use-case module in above-mentioned case management system can also be numbered, according to each test case
The number of the use-case module at place and the quantity of the similar test case in the module generate corresponding unique initial ID.By
It can be with employing mode, for example, therefore Arabic numerals and English alphabet etc. are not just made specific herein in numbering
It elaborates.
It can be seen from the above, determine that the use-case of test case is numbered by the above method, the corresponding use-case of each test case
Number is all unique, and each use-case number can be very good to embody test scene, the test function of the test case
Etc. attributive character, meanwhile, by use-case number in include characteristic ID, may be implemented to the control of the quantity of similar test case,
Be conducive to the determination of later period evaluating result.
Step S103, for each test case, produced by acquisition tests software under testing using the test case
Bug, as the corresponding test bug of the test case.
In this step, it for each test case, when being tested using the test case software under testing, obtains
Bug caused by testing, as the corresponding test bug of the test case.
Specifically, being illustrated by taking the functional test of word as an example, it is assumed that now to test the function of the lookup keyword of word
Can, corresponding test case is mainly, and the keyword to be searched is keyed in searching column, it is contemplated that effect be literary in test
In shelves, the page jumps to the position where the keyword of lookup automatically, but when actual test, and word does not have showing for any response
As thinking bug occur at this time, which is exactly the corresponding test bug generated of the test case.
Step S104 will be corresponding with the use-case number of the test case of test bug for each test bug of generation,
It is associated with test bug, obtains the incidence relation between test bug and use-case number.
In this step, each test bug that can be generated for test, will be corresponding with the test case of test bug
Use-case number, mark in test bug, with marked in test bug use-case number indicate test bug and use-case number
Between incidence relation.
Specifically, in each test bug that can be generated in test, it is in the form of a flag, test bug is corresponding
The use-case of test case is numbered, and is marked in test bug, to indicate being associated between test bug and use-case number
Relationship, the incidence relation being indirectly indicative between the corresponding use-case number of the test case and test bug.For example, above-mentioned survey
Try the function of the lookup keyword of word, it is assumed that occur then compiling the use-case of its corresponding test case without response phenomenon
Labelled notation is in corresponding test bug.
In embodiments of the present invention, the specific location of use-case number label, can freely set, example as the case may be
Such as, it can mark on the corresponding title of each test bug, can also mark in the detailed description of each test bug, e.g.,
At the positions such as remarks.
Step S105 is based on incidence relation, determines the evaluating result of software under testing.
In this step, it can be based on incidence relation, numbered according to the use-case marked in test bug, statistics use-case number
In the number that occurs of each attributive character；Compare whether the number that each attributive character occurs is greater than preset threshold value；According to what is compared
As a result and each attributive character numbers associated test bug to application examples, determines test result, the test analysis knot of software under testing
Fruit and comments, as evaluating result.
Specifically, the incidence relation between bug is numbered and tested based on use-case, according to the use marked in each test bug
Characteristic ID in example number indicates attributive character, corresponding time occurred of the statistics attributive character such as special scenes or specific function
Number, if the quantity of the number is greater than preset threshold value, corresponding scene module or functional module etc. are likely to occur problem,
For these problems module, detailed description in binding test bug determines test result, the Measurement results of software under testing
And comments, as evaluating result.
For example, an existing software under testing needs to carry out system testing comprising performance test, ui testing, compatibility
Property test, multiple tests such as safety test and interface testing, complete corresponding test bug acquisition according to above-mentioned steps, and
After incidence relation determines.Assuming that preset threshold testing bug quantity is 100, compiled according to associated use-case in test bug
Number, the test bug that statistics discovery performance test generates reaches 200, and the test bug that compatibility test generates reaches 500,
He tests the bug quantity found significantly lower than preset threshold value, at this point it is possible to generate according to performance test and compatibility test
Test bug in detailed description, the test result of available software under testing, and according to test result to software under testing carry out
Analysis proposes comments, determines evaluating result.For example, the performance and compatibility of above-mentioned software under testing are apparently without reaching
The reason of the problem of exploitation requires, and is shown according to test bug, problem analysis occurs, the module etc. for specifically needing to modify.
It in embodiments of the present invention, can be according to the assessment in evaluating result in the evaluating result for determining software under testing
Opinion increases test case, deleted or is modified on the basis of above-mentioned test case, as testing institute next time
The test case needed.It, can be for the survey in above-mentioned performance test and compatibility test module by taking above-mentioned system testing as an example
Example on probation is modified, or increases corresponding test case, tests the less ui testing module of bug for generating,
Interface testing module etc. then can the quantity appropriate that reduce test case, or to corresponding test case is modified, make it more
Add optimization etc., using test case adjusted as testing required test case next time.
Further, assessment of the embodiment of the present invention for software under testing, can be continuous with the version of software under testing
It alternates, version is continued to optimize in realization.As shown in figure 3, the software under testing of current version is directed to, according to the side in step S101
Method, multiple test cases needed for obtaining test, is stored in case management system, case management system is based on, according to step
Method in S102 determines the use-case number of each test case.According to the method in step S103, case management system is called
Test case in system, and test case the testing to test software under testing of calling is executed, obtain the survey that test generates
Try bug.According to the method in step S104, in bug management system, being associated between use-case number and test bug is determined
System.Evaluating result is determined according to the incidence relation of each test bug and use-case number according to the method in step S105.Most
Afterwards according to evaluating result, the test case of positive feedback adjusted in case management system specifically can increase, deletes or modify
Test case in case management system, and test case adjusted is used for the execution that next round is tested.And then to current
The software under testing of next version of version is tested, and version is continued to optimize in realization, forms the good of software under testing version
Property iteration.
In conclusion the determination method of the software evaluating result provided through the embodiment of the present invention, is determining evaluating result
When, the use-case number institute marked in each test bug can be counted directly according to the incidence relation of test bug and use-case number
The problem of embodying module determines that the evaluating result of software under testing.Compared with prior art, the embodiment of the present invention is asked in statistics
When inscribing module, where the problem of testing bug, software under testing can be obtained, especially with the continuous of software under testing
Optimization, needed for test case number will be continuously increased, but the test bug number of output will be reduced constantly, using of the invention real
Example is applied, the time of statistics will be significantly shorter, to improve the efficiency of assessment.
Based on same inventive concept, according to a kind of determination side for software evaluating result that the embodiments of the present invention provide
Method, the embodiment of the invention also provides a kind of determining devices of software test result, as shown in figure 4, may include with lower module:
Test case obtains module 401, carries out testing required multiple test cases for software under testing for obtaining；
Use-case number determining module 402 is used for for each test case, each attributive character based on the test case,
It is determined to indicate the use-case number of each attributive character of the test case；
It tests bug and obtains module 403, for being directed to each test case, obtain using the test case to software under testing
It carries out testing generated bug, as the corresponding test bug of the test case；
Incidence relation determining module 404, for the test of test bug will to be corresponding with for each test bug generated
The use-case of use-case is numbered, and is associated with test bug, and the incidence relation between test bug and use-case number is obtained；
Evaluating result determining module 405 determines the evaluating result of software under testing for being based on incidence relation.
Further, use-case number determining module 402 may include:
ID acquisition submodule, for obtaining the characteristic ID and the test case of each attributive character of the test case
Unique initial ID；
Use-case number generates submodule, for generate include the test case each attributive character characteristic ID and only
The use-case of one initial ID is numbered, and the use-case as the test case is numbered.
Further, above-mentioned apparatus can also include:
Similar test case statistical module compiles application examples according to the test case for being directed to each test case
Characteristic ID in number counts the test case with same characteristic features ID, as similar test case；
Use-case number redefine module, for when the quantity of similar test case be greater than preset use-case quantity when, needle
The survey is redefined by increasing the test case to the attributive character in application examples number to each similar test case
The use-case number of example on probation.
Further, each attributive character at least may include one of following attributive character:
Scene characteristic, functional character and operation behavior feature when software under testing is tested.
Further, incidence relation determining module 404 will be corresponded to specifically for each test bug generated for test
There is the use-case of the test case of test bug to number, mark in test bug, is numbered with the use-case marked in test bug
Indicate the incidence relation between test bug and use-case number.
Further, evaluating result determining module 405 may include:
Number statistic submodule numbers according to the use-case marked in test bug for being based on incidence relation, counts use-case
The number that each attributive character occurs in number；
Whether Comparative sub-module, the number occurred for more each attributive character are greater than preset threshold value；
Evaluating result determines submodule, is used for according to the result of the comparison and each attributive character is associated to application examples number
Bug is tested, the test result, Measurement results and comments of software under testing are determined, as evaluating result.
Further, above-mentioned apparatus can also include:
Test case reacquires module, for obtaining according to the comments in evaluating result, carries out to test case
The test case obtained after increasing, delete or modifying, as testing required test case next time.
The embodiment of the invention also provides a kind of electronic equipment, as shown in figure 5, include processor 501, communication interface 502,
Memory 503 and communication bus 504, wherein processor 501, communication interface 502, memory 503 are complete by communication bus 504
At mutual communication,
Memory 503, for storing computer program；
Processor 501 when for executing the program stored on memory 503, realizes following steps:
It obtains and carries out testing required multiple test cases for software under testing；
For each test case, each attributive character based on the test case is determined to indicate the test case
The use-case of each attributive character is numbered；
For each test case, acquisition carries out software under testing using the test case to test generated bug, as
The corresponding test bug of the test case；
For each test bug of generation, it will be corresponding with the use-case number of the test case of test bug, with the test
Bug is associated, and obtains the incidence relation between test bug and use-case number；
Based on incidence relation, the evaluating result of software under testing is determined.
The communication bus that above-mentioned electronic equipment is mentioned can be Peripheral Component Interconnect standard (Peripheral Component
Interconnect, PCI) bus or expanding the industrial standard structure (Extended Industry Standard
Architecture, EISA) bus etc..The communication bus can be divided into address bus, data/address bus, control bus etc..For just
It is only indicated with a thick line in expression, figure, it is not intended that an only bus or a type of bus.
Communication interface is for the communication between above-mentioned electronic equipment and other equipment.
Memory may include random access memory (Random Access Memory, RAM), also may include non-easy
The property lost memory (Non-Volatile Memory, NVM), for example, at least a magnetic disk storage.Optionally, memory may be used also
To be storage device that at least one is located remotely from aforementioned processor.
Above-mentioned processor can be general processor, including central processing unit (Central Processing Unit,
CPU), network processing unit (Network Processor, NP) etc.；It can also be digital signal processor (Digital Signal
Processing, DSP), it is specific integrated circuit (Application Specific Integrated Circuit, ASIC), existing
It is field programmable gate array (Field-Programmable Gate Array, FPGA) or other programmable logic device, discrete
Door or transistor logic, discrete hardware components.
In another embodiment provided by the invention, a kind of computer readable storage medium is additionally provided, which can
It reads to be stored with computer program in storage medium, the computer program realizes any of the above-described software assessment when being executed by processor
As a result the step of determination method.
In another embodiment provided by the invention, a kind of computer program product comprising instruction is additionally provided, when it
When running on computers, so that computer executes the determination method of any software evaluating result in above-described embodiment.
In the above-described embodiments, can come wholly or partly by software, hardware, firmware or any combination thereof real
It is existing.When implemented in software, it can entirely or partly realize in the form of a computer program product.The computer program
Product includes one or more computer instructions.When loading on computers and executing the computer program instructions, all or
It partly generates according to process or function described in the embodiment of the present invention.The computer can be general purpose computer, dedicated meter
Calculation machine, computer network or other programmable devices.The computer instruction can store in computer readable storage medium
In, or from a computer readable storage medium to the transmission of another computer readable storage medium, for example, the computer
Instruction can pass through wired (such as coaxial cable, optical fiber, number from a web-site, computer, server or data center
User's line (DSL)) or wireless (such as infrared, wireless, microwave etc.) mode to another web-site, computer, server or
Data center is transmitted.The computer readable storage medium can be any usable medium that computer can access or
It is comprising data storage devices such as one or more usable mediums integrated server, data centers.The usable medium can be with
It is magnetic medium, (for example, floppy disk, hard disk, tape), optical medium (for example, DVD) or semiconductor medium (such as solid state hard disk
Solid State Disk (SSD)) etc..
It should be noted that, in this document, relational terms such as first and second and the like are used merely to a reality
Body or operation are distinguished with another entity or operation, are deposited without necessarily requiring or implying between these entities or operation
In any actual relationship or order or sequence.Moreover, the terms "include", "comprise" or its any other variant are intended to
Non-exclusive inclusion, so that the process, method, article or equipment including a series of elements is not only wanted including those
Element, but also including other elements that are not explicitly listed, or further include for this process, method, article or equipment
Intrinsic element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that
There is also other identical elements in process, method, article or equipment including the element.
Each embodiment in this specification is all made of relevant mode and describes, same and similar portion between each embodiment
Dividing may refer to each other, and each embodiment focuses on the differences from other embodiments.Especially for device,
For the embodiments such as electronic equipment, since it is substantially similar to the method embodiment, so being described relatively simple, related place ginseng
See the part explanation of embodiment of the method.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the scope of the present invention.It is all
Any modification, equivalent replacement, improvement and so within the spirit and principles in the present invention, are all contained in protection scope of the present invention
It is interior.
Claims (15)
1. a kind of determination method of software evaluating result characterized by comprising
It obtains and carries out testing required multiple test cases for software under testing；
For each test case, each attributive character based on the test case is determined to indicate the test case
The use-case of each attributive character is numbered；
For each test case, acquisition carries out the software under testing using the test case to test generated bug,
As the corresponding test bug of the test case；
For each test bug of generation, the use-case number of the test case of test bug will be corresponding with, with test bug into
Row association obtains the incidence relation between test bug and use-case number；
Based on the incidence relation, the evaluating result of the software under testing is determined.
2. the method according to claim 1, wherein each attributive character based on the test case, determines
It can indicate the use-case number of each attributive character of the test case, comprising:
Obtain the characteristic ID of each attributive character of the test case and unique initial ID of the test case；
Generation includes that the characteristic ID of each attributive character of the test case and the use-case of unique initial ID are numbered, as
The use-case of the test case is numbered.
3. according to the method described in claim 2, it is characterized in that, each test case is directed to described, based on the survey
Each attributive character of example on probation is determined to after the use-case number for indicating each attributive character of the test case, further includes:
For each test case, according to the test case to the characteristic ID in application examples number, statistics has identical
The test case of characteristic ID, as similar test case；
When the quantity of the similar test case is greater than preset use-case quantity, for similar test case described in each,
By increasing the test case to the attributive character in application examples number, the use-case number of the test case is redefined.
4. method according to claim 1 or 2, which is characterized in that each attributive character includes at least such as properties spy
One of sign:
Scene characteristic, functional character and operation behavior feature when the software under testing is tested.
5. the method according to claim 1, wherein each test bug for generation, will be corresponding with this
The use-case number for testing the test case of bug, is associated with test bug, obtains the pass between test bug and use-case number
Connection relationship, comprising:
For each test bug that test generates, it will be corresponding with the use-case number of the test case of test bug, marked at this
It tests in bug, the incidence relation between test bug and use-case number is indicated with the use-case number marked in test bug.
6. according to the method described in claim 5, it is characterized in that, it is described be based on the incidence relation, determine described to be measured soft
The evaluating result of part, comprising:
It based on the incidence relation, is numbered according to the use-case marked in the test bug, each attributive character in statistics use-case number
The number of appearance；
Compare whether the number that each attributive character occurs is greater than preset threshold value；
According to the result of the comparison and each attributive character numbers associated test bug to application examples, determines the software under testing
Test result, Measurement results and comments, as evaluating result.
7. according to the method described in claim 6, it is characterized in that, being determined described to be measured described based on the incidence relation
After the evaluating result of software, further includes:
It obtains according to the comments in the evaluating result, after the test case is increased, deleted or modified
The test case arrived, as testing required test case next time.
8. a kind of determining device of software evaluating result characterized by comprising
Test case obtains module, carries out testing required multiple test cases for software under testing for obtaining；
Use-case number determining module, for being directed to each test case, each attributive character based on the test case is determined
It can indicate the use-case number of each attributive character of the test case；
It tests bug and obtains module, for being directed to each test case, obtain using the test case to the software under testing
It carries out testing generated bug, as the corresponding test bug of the test case；
Incidence relation determining module, for the test case of test bug will to be corresponding with for each test bug generated
Use-case number, is associated with test bug, obtains the incidence relation between test bug and use-case number；
Evaluating result determining module determines the evaluating result of the software under testing for being based on the incidence relation.
9. device according to claim 8, which is characterized in that the use-case number determining module, comprising:
ID acquisition submodule, for obtain each attributive character of the test case characteristic ID and the test case it is unique
Initial ID；
Use-case number generate submodule, for generate include the test case each attributive character characteristic ID and it is described only
The use-case of one initial ID is numbered, and the use-case as the test case is numbered.
10. device according to claim 9, which is characterized in that described device, further includes:
Similar test case statistical module, for being directed to each test case, according to the test case in application examples number
The characteristic ID, count have same characteristic features ID test case, as similar test case；
Use-case number redefine module, for when the quantity of the similar test case be greater than preset use-case quantity when, needle
Each similar test case is redefined by increasing the test case to the attributive character in application examples number
The use-case of the test case is numbered.
11. device according to claim 8 or claim 9, which is characterized in that each attributive character includes at least such as properties spy
One of sign:
Scene characteristic, functional character and operation behavior feature when the software under testing is tested.
12. device according to claim 8, which is characterized in that the incidence relation determining module is specifically used for for survey
Raw each test bug is test-manufactured, the use-case number of the test case of test bug will be corresponding with, marked in test bug,
The incidence relation between test bug and use-case number is indicated with the use-case number marked in test bug.
13. device according to claim 12, which is characterized in that the evaluating result determining module, comprising:
Number statistic submodule is numbered, statistics for being based on the incidence relation according to the use-case marked in the test bug
The number that each attributive character occurs in use-case number；
Whether Comparative sub-module, the number occurred for each attributive character are greater than preset threshold value；
Evaluating result determines submodule, is used for according to the result of the comparison and each attributive character numbers associated test to application examples
Bug determines the test result, Measurement results and comments of the software under testing, as evaluating result.
14. device according to claim 13, which is characterized in that described device, further includes:
Test case reacquires module, for obtaining according to the comments in the evaluating result, to the test case
The test case obtained after being increased, deleted or being modified, as testing required test case next time.
15. a kind of electronic equipment, which is characterized in that including processor, communication interface, memory and communication bus, wherein processing
Device, communication interface, memory complete mutual communication by communication bus；
Memory, for storing computer program；
Processor when for executing the program stored on memory, realizes method and step as claimed in claim 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810816785.8A CN109062794B (en) | 2018-07-24 | 2018-07-24 | Method and device for determining software evaluation result and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810816785.8A CN109062794B (en) | 2018-07-24 | 2018-07-24 | Method and device for determining software evaluation result and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109062794A true CN109062794A (en) | 2018-12-21 |
| CN109062794B CN109062794B (en) | 2022-04-22 |
Family
ID=64836328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810816785.8A Active CN109062794B (en) | 2018-07-24 | 2018-07-24 | Method and device for determining software evaluation result and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109062794B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857660A (en) * | 2019-01-25 | 2019-06-07 | 北京达佳互联信息技术有限公司 | Project measurement method, system, device and computer readable storage medium |
| CN111752833A (en) * | 2020-06-23 | 2020-10-09 | 南京领行科技股份有限公司 | Software quality system approval method, device, server and storage medium |
| CN112115049A (en) * | 2020-08-27 | 2020-12-22 | 北京奇艺世纪科技有限公司 | Application program testing method, device, equipment and computer readable storage medium |
| CN112363928A (en) * | 2020-11-10 | 2021-02-12 | 网易（杭州）网络有限公司 | Test case processing method and device, processor and electronic device |
| CN112416768A (en) * | 2020-11-20 | 2021-02-26 | 深圳开源互联网安全技术有限公司 | Interactive security vulnerability detection method, system, device and readable storage medium |
| CN113268419A (en) * | 2021-05-19 | 2021-08-17 | 北京金山云网络技术有限公司 | Method, device, equipment and storage medium for generating test case optimization information |
| CN113688060A (en) * | 2021-10-26 | 2021-11-23 | 深圳市信润富联数字科技有限公司 | Defect management method, device, equipment, storage medium and computer program product |
| CN114996167A (en) * | 2022-08-03 | 2022-09-02 | 成都星联芯通科技有限公司 | Test case management method and device, storage medium and electronic equipment |
| CN115809203A (en) * | 2023-02-07 | 2023-03-17 | 杭州罗莱迪思科技股份有限公司 | Software test case dynamic nesting method, device and application thereof |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186456A (en) * | 2011-12-29 | 2013-07-03 | 北京新媒传信科技有限公司 | Method and device for testing system |
| CN103186466A (en) * | 2011-12-31 | 2013-07-03 | 中国银联股份有限公司 | Information interaction device and method based on automatic generation of associated test cases |
| CN103257918A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Project test procedure management method based on software testing and evaluation platform |
| US20170192880A1 (en) * | 2016-01-06 | 2017-07-06 | Hcl Technologies Limited | Defect prediction |
-
2018
- 2018-07-24 CN CN201810816785.8A patent/CN109062794B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103186456A (en) * | 2011-12-29 | 2013-07-03 | 北京新媒传信科技有限公司 | Method and device for testing system |
| CN103186466A (en) * | 2011-12-31 | 2013-07-03 | 中国银联股份有限公司 | Information interaction device and method based on automatic generation of associated test cases |
| CN103257918A (en) * | 2012-02-16 | 2013-08-21 | 广州博纳信息技术有限公司 | Project test procedure management method based on software testing and evaluation platform |
| US20170192880A1 (en) * | 2016-01-06 | 2017-07-06 | Hcl Technologies Limited | Defect prediction |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109857660A (en) * | 2019-01-25 | 2019-06-07 | 北京达佳互联信息技术有限公司 | Project measurement method, system, device and computer readable storage medium |
| CN111752833A (en) * | 2020-06-23 | 2020-10-09 | 南京领行科技股份有限公司 | Software quality system approval method, device, server and storage medium |
| CN111752833B (en) * | 2020-06-23 | 2022-08-26 | 南京领行科技股份有限公司 | Software quality system approval method, device, server and storage medium |
| CN112115049B (en) * | 2020-08-27 | 2023-06-02 | 北京奇艺世纪科技有限公司 | Application program testing method, device, equipment and computer readable storage medium |
| CN112115049A (en) * | 2020-08-27 | 2020-12-22 | 北京奇艺世纪科技有限公司 | Application program testing method, device, equipment and computer readable storage medium |
| CN112363928A (en) * | 2020-11-10 | 2021-02-12 | 网易（杭州）网络有限公司 | Test case processing method and device, processor and electronic device |
| CN112363928B (en) * | 2020-11-10 | 2023-08-22 | 网易（杭州）网络有限公司 | Processing method and device of test case, processor and electronic device |
| CN112416768A (en) * | 2020-11-20 | 2021-02-26 | 深圳开源互联网安全技术有限公司 | Interactive security vulnerability detection method, system, device and readable storage medium |
| CN113268419A (en) * | 2021-05-19 | 2021-08-17 | 北京金山云网络技术有限公司 | Method, device, equipment and storage medium for generating test case optimization information |
| CN113268419B (en) * | 2021-05-19 | 2024-04-09 | 北京金山云网络技术有限公司 | Method, device, equipment and storage medium for generating test case optimization information |
| CN113688060A (en) * | 2021-10-26 | 2021-11-23 | 深圳市信润富联数字科技有限公司 | Defect management method, device, equipment, storage medium and computer program product |
| CN114996167B (en) * | 2022-08-03 | 2022-11-01 | 成都星联芯通科技有限公司 | Test case management method and device, storage medium and electronic equipment |
| CN114996167A (en) * | 2022-08-03 | 2022-09-02 | 成都星联芯通科技有限公司 | Test case management method and device, storage medium and electronic equipment |
| CN115809203B (en) * | 2023-02-07 | 2023-04-25 | 杭州罗莱迪思科技股份有限公司 | Dynamic nesting method and device for software test cases and application of dynamic nesting method and device |
| CN115809203A (en) * | 2023-02-07 | 2023-03-17 | 杭州罗莱迪思科技股份有限公司 | Software test case dynamic nesting method, device and application thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109062794B (en) | 2022-04-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109062794A (en) | A kind of the determination method, apparatus and electronic equipment of software evaluating result | |
| CN109062809B (en) | Online test case generation method and device and electronic equipment | |
| US8918678B2 (en) | Functional testing of a processor design | |
| Ocariza Jr et al. | JavaScript errors in the wild: An empirical study | |
| KR100849223B1 (en) | Method of testing USB apparatus and system thereof | |
| CN105068929A (en) | Test script generation method, test script generation device, testing method, testing device and testing system | |
| US20030018461A1 (en) | Simulation monitors based on temporal formulas | |
| US20110055777A1 (en) | Verification of Soft Error Resilience | |
| US20160306736A1 (en) | Translation verification testing | |
| US10372856B2 (en) | Optimizing constraint solving by rewriting at least one bit-slice constraint | |
| US11003817B2 (en) | Hard error simulation and usage thereof | |
| US10830818B2 (en) | Ensuring completeness of interface signal checking in functional verification | |
| US20120173498A1 (en) | Verifying Correctness of a Database System | |
| US8909579B2 (en) | Identifying invariant candidates based on proofs | |
| CN108647533B (en) | Automatic generation method of safety assertion for detecting hardware trojan | |
| US20090112552A1 (en) | Method, System and Program Product for Reporting Temporal Information Regarding Count Events of a Simulation | |
| Altisen et al. | SASA: a SimulAtor of Self-stabilizing Algorithms | |
| CN115422865B (en) | Simulation method and device, computing equipment and computer readable storage medium | |
| JP2014134842A (en) | Verification device and verification method | |
| CN112631852B (en) | Macro checking method, macro checking device, electronic equipment and computer readable storage medium | |
| CN108875374A (en) | Malice PDF detection method and device based on document node type | |
| US20230011129A1 (en) | Log analyzer for fault detection | |
| EP3553681B1 (en) | Method and apparatus for error test coverage determination for a circuit by simulation | |
| US7650579B2 (en) | Model correspondence method and device | |
| US10437716B2 (en) | Method and apparatus for coverage analysis of SRT look-up table |
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 |