CN104317725A - Computer implementation method of software testing, computer and system - Google Patents
Computer implementation method of software testing, computer and system Download PDFInfo
- Publication number
- CN104317725A CN104317725A CN201410657171.1A CN201410657171A CN104317725A CN 104317725 A CN104317725 A CN 104317725A CN 201410657171 A CN201410657171 A CN 201410657171A CN 104317725 A CN104317725 A CN 104317725A
- Authority
- CN
- China
- Prior art keywords
- risk
- test
- item
- risk item
- target software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a computer implementation method of software testing, a computer and a system, and belongs to the testing field. The method comprises determining at least one risk item of the target software to be tested at present according to first input information triggered by a user on an input device, determining a risk grade corresponding to the at least one risk item according to second input information triggered by the user on the input device, and testing the target software according to the at least one risk item and the risk grade corresponding to the at least one risk item. The computer implementation method of the software testing is capable of reducing the existing quality risks by use of testing measures special for the risks, and therefore, the efficiency and reliability of testing can be improved.
Description
Technical field
The present invention relates to field tests, the computer implemented method of particularly a kind of software test, computing machine and system.
Background technology
Instantly, venture analysis and countermeasure are applied in the work in software test field also in the middle of progressively exploring, but in reduction testing cost, software test venture analysis are not are not yet deeply systematically researched and analysed.The quality certification system of China's software industry is also not bery perfect, at home, the theory of software test venture analysis and research or emerging field, for a long time, during China's software enterprise's product development, due to software test think little of cause testing cost the most easily to be compressed, even " cut down ", cause China's speed measuring with software low.Usual need-based Test Strategy, should analyze demand in the test preparatory stage, identify that the test of test condition, design and implementation carrys out coverage test condition, and safeguards from test and get back to the trackability of demand.Performing and improving test phase, tester's testing results is also reported the result, and comprise report based on these tests, which which demand is met and do not meet.
But need-based Test Strategy cannot reduce the impact of risk item on this test process, reduce efficiency and the reliability of test.
Summary of the invention
In order to solve the problem of prior art, embodiments provide a kind of computer implemented method of software test, computing machine and system.Described technical scheme is as follows:
First aspect, provide a kind of computer implemented method of software test, described method comprises:
According to the first input information that user triggers at input equipment, determine at least one risk item of the current target software that will test;
According to the second input information that described user triggers at described input equipment, determine the risk class corresponding respectively with at least one risk item described;
Distinguish corresponding risk class according at least one risk item described and at least one risk item described and described, described target software is tested.
In conjunction with first aspect, in the implementation that the first is possible, at least one risk item described in described basis and at least one risk item described and described distinguish corresponding risk class, carry out test comprise described target software:
According to the height of risk class, at least one risk item described is sorted;
From the risk item that risk class is the highest, successively described target software is tested.
Second aspect, provides a kind of computing machine, and described computing machine comprises:
Processing unit, for the first input information triggered at input equipment according to user, determines at least one risk item of the current target software that will test;
Described processing unit also for, according to the second input information that described user triggers at described input equipment, determine the risk class corresponding respectively with described at least one risk item;
Test cell, for distinguishing corresponding risk class according at least one risk item described and at least one risk item described and described, tests described target software.
In conjunction with second aspect, in the implementation that the first is possible, described test cell specifically for:
According to the height of risk class, at least one risk item described is sorted;
From the risk item that risk class is the highest, successively described target software is tested.
The third aspect, provide a kind of computer implemented system of software test, described system comprises:
Input equipment, for receiving first trigger pip of user, generating the first input information, and receiving second trigger pip of user, generate the second input information;
Memory device, for storing the multiple softwares at least comprising target software;
And, the computing machine described in the first possible implementation of second aspect or second aspect.
The embodiment of the present invention provides a kind of computer implemented method of software test, computing machine and system, by distinguishing corresponding risk class according at least one risk item with at least one risk item, target software is tested, by the special test measure for risk, reduce the quality risk existed, improve efficiency and the reliability of test.
Accompanying drawing explanation
In order to be illustrated more clearly in the technical scheme in the embodiment of the present invention, below the accompanying drawing used required in describing embodiment is briefly described, apparently, accompanying drawing in the following describes is only some embodiments of the present invention, for those of ordinary skill in the art, under the prerequisite not paying creative work, other accompanying drawing can also be obtained according to these accompanying drawings.
Fig. 1 is the computer implemented method flow diagram of a kind of software test that the embodiment of the present invention provides;
Fig. 2 is the computer implemented method flow diagram of a kind of software test that the embodiment of the present invention provides;
Fig. 3 is a kind of computer organization schematic diagram that the embodiment of the present invention provides;
Fig. 4 is the computer implemented system schematic of a kind of software test that the embodiment of the present invention provides.
Embodiment
For making the object, technical solutions and advantages of the present invention clearly, below in conjunction with accompanying drawing, embodiment of the present invention is described further in detail.
The embodiment of the present invention provides a kind of computer implemented method of software test, and with reference to shown in Fig. 1, the method comprises:
101, according to the first input information that user triggers at input equipment, at least one risk item of the current target software that will test is determined.
102, according to the second input information that user triggers at input equipment, the risk class corresponding respectively with at least one risk item is determined.
103, according at least one risk item and the risk class corresponding respectively with at least one risk item, target software is tested.
The embodiment of the present invention provides a kind of computer implemented method of software test, by distinguishing corresponding risk class according at least one risk item with at least one risk item, target software is tested, by the special test measure for risk, reduce the quality risk existed, improve efficiency and the reliability of test.
The embodiment of the present invention provides a kind of computer implemented method of software test, and with reference to shown in Fig. 2, the method comprises:
201, according to the first input information that user triggers at input equipment, at least one risk item of the current target software that will test is determined.
From the venture analysis that the angle used based on mass property and user is carried out, export record, can from aspects such as (input, code path, state, the data be stored and running environment) to consider the possibility of quality risk.Recorded information content template is as form 1:
Form
Illustrate:
Quality risk: the Risk list obtained by venture analysis.
Possibility occurrence: the possibility that problem occurs: 1=is very high, and 2=is high, and in 3=, 4=is low, and 5=is very low.
The impact caused: the impact caused after generation: 1=is very high, and 2=is high, in 3=, 4=is low, and 5=is very low.
Risk class: the measured value of problem definition risk, determines risk class: the risk of high likelihood, high impact has limit priority, stress test.Project stakeholder directly determines the priority of each risk according to the situation coupling system function of risk reality.
Traceability: the tracked information being traceable to demand, design or other risk bases.
Before step 201, also should, at the project testing initial stage, need to organize project stakeholder to identify concrete quality risk item, then to this risk item of computer input.
Afterwards, then on the possibility occurred according to risk and the common evaluation and grading grade of impact after occurring, and to this risk class of computer input.
202, according to the second input information that user triggers at input equipment, the risk class corresponding respectively with at least one risk item is determined.
Risk class generally also can be determined by following formula: the impact of the possibility of risk class=generation × cause.
Test degree: according to risk class, determines the degree of testing.
Exemplary, risk class can be as shown in table 2.
Form 2
203, according to the height of risk class, at least one risk item described is sorted.
204, from the risk item that risk class is the highest, successively target software is tested.
Concrete, first carry out test design based on venture analysis.
Risk based on each function items listed in Risk list carries out test design one by one, comprise summary test design, DCO design and test case and write three phases, mainly the contents such as Test Strategy, method of testing, testing tool, input, expected results are carried out clearly.Detailed process can be:
Determine Test Strategy, mainly the characteristic of each risk item is described, and determines concrete testing tool and method of testing according to the characteristic of risk item.
Determine the test use cases of this risk, and carry out clearly, comprising the common method based on Specification to the Black-box Testing method that this test use cases adopts: equivalence class, boundary value, cause-and-effect diagram, decision table, State Transferring, scene method etc.; Based on the method such as exploration, attack, classification of defects technology of experience.
Concrete test case is write based on the method for testing for this risk determined in DCO design, the difference test design of multiple function items can be comprised, need the contents such as the test point of clear and definite every bar test case, test data, input and expection correct result, concrete use-case form can be different according to detailed programs.
Finally, then from the risk item that risk class is the highest, successively described target software is tested.
Optionally, all right monitoring and test process, concrete observation process can be:
Risk class and test manpower are mated, risk class is higher, drops into test manpower more; Risk class and testing sequence are mated.Need in the project regularly according to the information got, risk of reappraising and risk class, this can make us again for test and defect divide priority, redistributes test job amount, and takes testing and control measure simultaneously.The part higher to risk carries out test can find relatively prior place in more defect or test macro, and risk is higher, more early arranges test, risk class and test manpower is mated.
Because manpower distributes and the arrangement of testing sequence, along with test is carried out, total residual mass risk class can foreseeable reduction.By the trackability between maintenance test and risk, between oriented defect and risk, we can report test result according to remaining risk.When the risk continuing test has exceeded the risk announcing test end, project stakeholder can determine to announce that test terminates.
In measuring executing process, need pay close attention to the risk of test risk itself, it is unreasonable that such as priority divides.Can be participated in by many personnel, tester participates in evaluation, the tested object of low priority be carried out to the generation that the method for exploratory testing etc. carrys out evasion as far as possible.
By analyzing the accepted rank of residue risk, for the risk record left over, test result and project status, the subject matter of analytic system current state and existence, helps the nearlyer step of project stakeholder to understand system, and makes the decision whether can issued.
The above-mentioned strategy based on venture analysis, its feature is, is determining in priority: from user perspective, and the possibility occurred based on risk and the order of severity of generation determine the priority orders of testing from breadth and depth two aspect.The measuring technology matched according to the risk class of different risk item pro-rata manpower, selection and risk class in test activity, first to process most important quality risk by risk class, finally just process those secondary risks.Tester ensures that together with project team all personnel the priority level initializing of risk class and solution adapt to its risk class.
The above-mentioned strategy based on venture analysis, its feature is, determining in test completeness: reach common understanding between QA Manager and project manager, function for different priorities takes different test modes, the object minimum to priority can not be tested in the unallowed situations such as time, thus ensures the balance between test mass and progress.In test plan and test execution, QA Manager carries out testing and control to all important project risks identified.Project risk rank is higher, and the control of implementation is stricter.
The above-mentioned strategy based on venture analysis, its feature is, in test is carried out, threaten the residual risk rank of mass of system progressively to reduce, and QA Manager is according to the risk class report test result of residue risk and project status.
Above method runs through whole software test lifecycle: reduce quality risk by testing results and searching defect, by risk mitigation, the emergency plan as necessary by plan ahead reduces project risk.Such as expert advice, colleague's experience, substep switching, cross-training, and carry out the worst plan, namely during system cisco unity malfunction, preparation developer carries out urgent exploitation and waits plan.Risk in project and risk class are reappraised according to new information termly.
The embodiment of the present invention provides a kind of computer implemented method of software test, by distinguishing corresponding risk class according at least one risk item with at least one risk item, target software is tested, by the special test measure for risk, reduce the quality risk existed, improve efficiency and the reliability of test.
The embodiment of the present invention provides a kind of computing machine 3, and with reference to shown in Fig. 3, the method comprises:
Processing unit 31, for the first input information triggered at input equipment according to user, determines at least one risk item of the current target software that will test;
Processing unit 31 also for, according to the second input information that user triggers at input equipment, determine the risk class respectively corresponding with at least one risk item;
Test cell 32, for according at least one risk item and the risk class corresponding respectively with at least one risk item, tests target software.
Optionally, test cell 32 specifically for:
According to the height of risk class, at least one risk item is sorted;
From the risk item that risk class is the highest, successively target software is tested.
The embodiment of the present invention provides a kind of computing machine, by according at least one risk item and the risk class corresponding respectively with at least one risk item, target software is tested, by the special test measure for risk, reduce the quality risk existed, improve efficiency and the reliability of test.
The embodiment of the present invention provides a kind of computer implemented system of software test, and with reference to shown in Fig. 4, this system comprises:
Input equipment 41, for receiving first trigger pip of user, generating the first input information, and receiving second trigger pip of user, generate the second input information;
Memory device 42, for storing the multiple softwares at least comprising target software;
And the computing machine 43 described in embodiment 3.
The embodiment of the present invention provides a kind of computer implemented system of software test, by distinguishing corresponding risk class according at least one risk item with at least one risk item, target software is tested, by the special test measure for risk, reduce the quality risk existed, improve efficiency and the reliability of test.
It should be noted that: the computing machine that above-described embodiment provides is when realizing a kind of computer implemented method of software test, only be illustrated with the division of above-mentioned each functional module, in practical application, can distribute as required and by above-mentioned functions and be completed by different functional modules, inner structure by computing machine is divided into different functional modules, to complete all or part of function described above.In addition, the computer implemented embodiment of the method for the computing machine that above-described embodiment provides and software test belongs to same design, and its specific implementation process refers to embodiment of the method, repeats no more here.
One of ordinary skill in the art will appreciate that all or part of step realizing above-described embodiment can have been come by hardware, the hardware that also can carry out instruction relevant by program completes, described program can be stored in a kind of computer-readable recording medium, the above-mentioned storage medium mentioned can be ROM (read-only memory), disk or CD etc.
The foregoing is only preferred embodiment of the present invention, not in order to limit the present invention, within the spirit and principles in the present invention all, any amendment done, equivalent replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (5)
1. a computer implemented method for software test, is characterized in that, described method comprises:
According to the first input information that user triggers at input equipment, determine at least one risk item of the current target software that will test;
According to the second input information that described user triggers at described input equipment, determine the risk class corresponding respectively with at least one risk item described;
Distinguish corresponding risk class according at least one risk item described and at least one risk item described and described, described target software is tested.
2. method according to claim 1, is characterized in that, at least one risk item described in described basis and at least one risk item described and described distinguish corresponding risk class, carry out test comprise described target software:
According to the height of risk class, at least one risk item described is sorted;
From the risk item that risk class is the highest, successively described target software is tested.
3. a computing machine, is characterized in that, described computing machine comprises:
Processing unit, for the first input information triggered at input equipment according to user, determines at least one risk item of the current target software that will test;
Described processing unit also for, according to the second input information that described user triggers at described input equipment, determine the risk class corresponding respectively with described at least one risk item;
Test cell, for distinguishing corresponding risk class according at least one risk item described and at least one risk item described and described, tests described target software.
4. computing machine according to claim 3, is characterized in that, described test cell specifically for:
According to the height of risk class, at least one risk item described is sorted;
From the risk item that risk class is the highest, successively described target software is tested.
5. a computer implemented system for software test, is characterized in that, described system comprises:
Input equipment, for receiving first trigger pip of user, generating the first input information, and receiving second trigger pip of user, generate the second input information;
Memory device, for storing the multiple softwares at least comprising target software;
And, the computing machine described in claim 3 or 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410657171.1A CN104317725A (en) | 2014-11-18 | 2014-11-18 | Computer implementation method of software testing, computer and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410657171.1A CN104317725A (en) | 2014-11-18 | 2014-11-18 | Computer implementation method of software testing, computer and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104317725A true CN104317725A (en) | 2015-01-28 |
Family
ID=52372960
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410657171.1A Pending CN104317725A (en) | 2014-11-18 | 2014-11-18 | Computer implementation method of software testing, computer and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104317725A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108604330A (en) * | 2015-10-06 | 2018-09-28 | 内特弗利克斯股份有限公司 | System and method for the safety of application and risk assessment and test |
| CN109859035A (en) * | 2019-02-02 | 2019-06-07 | 中国银行股份有限公司 | A kind of data processing method of application product functional test, apparatus and system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799822A (en) * | 2012-07-11 | 2012-11-28 | 中国信息安全测评中心 | Software running security measurement and estimation method based on network environment |
| CN102902622A (en) * | 2012-09-14 | 2013-01-30 | 广东电网公司电力调度控制中心 | Multi-computing-based software project test quantitative evaluating method and system |
| US20140040867A1 (en) * | 2012-08-03 | 2014-02-06 | Sap Ag | System test scope and plan optimization |
-
2014
- 2014-11-18 CN CN201410657171.1A patent/CN104317725A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102799822A (en) * | 2012-07-11 | 2012-11-28 | 中国信息安全测评中心 | Software running security measurement and estimation method based on network environment |
| US20140040867A1 (en) * | 2012-08-03 | 2014-02-06 | Sap Ag | System test scope and plan optimization |
| CN102902622A (en) * | 2012-09-14 | 2013-01-30 | 广东电网公司电力调度控制中心 | Multi-computing-based software project test quantitative evaluating method and system |
Non-Patent Citations (1)
| Title |
|---|
| 柳纯录: "《软件评测师教程》", 31 March 2005, 清华大学出版社 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108604330A (en) * | 2015-10-06 | 2018-09-28 | 内特弗利克斯股份有限公司 | System and method for the safety of application and risk assessment and test |
| CN109859035A (en) * | 2019-02-02 | 2019-06-07 | 中国银行股份有限公司 | A kind of data processing method of application product functional test, apparatus and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Hovorushchenko | Methodology of evaluating the sufficiency of information for software quality assessment according to ISO 25010 | |
| US10719302B2 (en) | Code origination data management for code assembly | |
| WO2019085061A1 (en) | Automatic test management method, apparatus and device for fund system, and storage medium | |
| CN102662833B (en) | Method for managing test cases | |
| Mondal et al. | A comparative study on the bug-proneness of different types of code clones | |
| Zhang et al. | Variability evolution and erosion in industrial product lines: a case study | |
| US10175952B2 (en) | Code origination data management for host placement | |
| Faizan et al. | Contemporary trends in defect prevention: A survey report | |
| CN102693460A (en) | Tester management system and method thereof | |
| Walkinshaw et al. | Are 20% of files responsible for 80% of defects? | |
| Mısırlı et al. | Different strokes for different folks: A case study on software metrics for different defect categories | |
| Marandi et al. | An impact of linear regression models for improving the software quality with estimated cost | |
| CN104317725A (en) | Computer implementation method of software testing, computer and system | |
| Alves et al. | Applying ISO/IEC 25010 Standard to prioritize and solve quality issues of automatic ETL processes | |
| Gong et al. | An induction to the development of software quality model standards | |
| Asplund et al. | Qualifying software tools, a systems approach | |
| Silva et al. | Towards making safety-critical systems safer: learning from mistakes | |
| Seehusen | A technique for risk-based test procedure identification, prioritization and selection | |
| CN104461870A (en) | Method and device for recording testing result | |
| Lazaar et al. | Fault localization in constraint programs | |
| Lakshmi et al. | An effective rank approach to software defect prediction using software metrics | |
| CN112612882B (en) | Review report generation method, device, equipment and storage medium | |
| Hofer et al. | Fault localization in the light of faulty user input | |
| Ronchieri et al. | A software quality model by using discriminant analysis predictive technique | |
| Tahir et al. | Combining dynamic analysis and visualization to explore the distribution of unit test suites |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150128 |
|
| RJ01 | Rejection of invention patent application after publication |