CN106874201A - Method of testing and device - Google Patents

Method of testing and device Download PDF

Info

Publication number
CN106874201A
CN106874201A CN201710079041.8A CN201710079041A CN106874201A CN 106874201 A CN106874201 A CN 106874201A CN 201710079041 A CN201710079041 A CN 201710079041A CN 106874201 A CN106874201 A CN 106874201A
Authority
CN
China
Prior art keywords
abnormality
software
tested
occurs
stability
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
Application number
CN201710079041.8A
Other languages
Chinese (zh)
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.)
Caxa Technology Co Ltd
Original Assignee
Caxa Technology 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 Caxa Technology Co Ltd filed Critical Caxa Technology Co Ltd
Priority to CN201710079041.8A priority Critical patent/CN106874201A/en
Publication of CN106874201A publication Critical patent/CN106874201A/en
Pending legal-status Critical Current

Links

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

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 discloses a kind of method of testing and device.Wherein, the method includes:During test assignment is performed, the abnormality that software to be tested occurs is obtained, wherein, abnormality is the state in the range of presetting;The situation that length occurs for the abnormality in the time period of scheduled duration is obtained, wherein, the situation that abnormality occurs includes:The abnormality that software to be tested occurs in different test equipments;The stability of the assessment of scenario software to be tested occurred according at least to abnormality.The present invention solves the technical problem of the measurement for not being directed to software stability in the prior art.

Description

Method of testing and device
Technical field
The present invention relates to software testing technology field, in particular to a kind of method of testing and device.
Background technology
With the development of computer internet technology, the application of software is popularized very much, for software reliability, is The stability of system is particularly important.Software reliability refers to that software product completes rule under conditions of regulation with the time interval of regulation Determine the ability of function, wherein, it is stipulated that condition refer to computer system directly related to running software state and software Input condition;The time interval of regulation refers to the actual run time of software;Predetermined function refers to provide given function, software The prerequisite function of product institute.The reliability direct relation of software the experience effect of user.If using the process of software In, encounter software systems collapse, machine of delaying, blue screen, without response etc. behavior of serious failure, easily to user bring data degradation, effect Rate is lost.Thus, how to verify, the stability of metric software system, to user with QA, counter-measure etc. be provided seem It is extremely important.
At present, the understanding to software stability is confined to a general concept or a kind of sensation mostly.For software stabilization The test of property, prior art makees accelerated test primarily directed to certain special scenes, or takes monkey method of testing, that is, obtain certain The specific data of scene, do derivation to predict probability that failure occurs in user etc. according to certain formula.
The scheme of prior art, refers to because software stability is only general in the reliability of software metrics system, Without measurement or the systems approach and thinking of test for software stability.And existing measurement system is mainly with failure (Bug) count as important statistical parameter, not for stability metric method.Further, since right in existing measurement system Software prediction is more with complicated empirical equation, and not intuitively, validity, poor in timeliness, the experience difference with real user are larger.
For above-mentioned problem, effective solution is not yet proposed at present.
The content of the invention
A kind of method of testing and device are the embodiment of the invention provides, at least to solve not to be directed to software in the prior art The technical problem of the measurement of stability.
A kind of one side according to embodiments of the present invention, there is provided method of testing, including:Performing the mistake of test assignment Cheng Zhong, obtains the abnormality that software to be tested occurs, wherein, abnormality is the state in the range of presetting;Obtain The situation that the abnormality in the time period that length is scheduled duration occurs is taken, wherein, the situation that abnormality occurs includes:Treat The abnormality that test software occurs in different test equipments;The assessment of scenario occurred according at least to abnormality is to be tested soft The stability of part.
Another aspect according to embodiments of the present invention, additionally provides a kind of test device, including:First acquisition unit, uses During execution test assignment, the abnormality that software to be tested occurs is obtained, wherein, abnormality is to set in advance State in fixed scope;Second acquisition unit, occurs for obtaining the abnormality in the time period that length is scheduled duration Situation, wherein, abnormality occur situation include:The abnormality that software to be tested occurs in different test equipments; Assessment unit, the stability of the assessment of scenario software to be tested for occurring according at least to abnormality
In embodiments of the present invention, by the way that during test assignment is performed, it is different that acquisition software to be tested occurs Normal state, wherein, abnormality is the state in the range of presetting;Obtain different in the time period that length is scheduled duration The situation that normal state occurs, wherein, the situation that abnormality occurs includes:What software to be tested occurred in different test equipments Abnormality;The stability of the assessment of scenario software to be tested occurred according at least to abnormality, has reached instant understanding software The stable state of system, and the purpose of countermeasure is provided in time according to the stable state, it is achieved thereby that reduction user loss, The technique effect of Consumer's Experience is improved, and then the technology solved in the prior art not for the measurement of software stability is asked Topic.
Brief description of the drawings
Accompanying drawing described herein is used for providing a further understanding of the present invention, constitutes the part of the application, this hair Bright schematic description and description does not constitute inappropriate limitation of the present invention for explaining the present invention.In the accompanying drawings:
Fig. 1 is a kind of method of testing flow chart according to embodiments of the present invention;
Fig. 2 is a kind of optional method of testing flow chart according to embodiments of the present invention;
Fig. 3 is a kind of optional method of testing flow chart according to embodiments of the present invention;
Fig. 4 is a kind of optional method of testing flow chart according to embodiments of the present invention;
Fig. 5 is a kind of preferred method of testing flow chart according to embodiments of the present invention;And
Fig. 6 is a kind of test device schematic diagram according to embodiments of the present invention.
Specific embodiment
In order that those skilled in the art more fully understand the present invention program, below in conjunction with the embodiment of the present invention Accompanying drawing, is clearly and completely described to the technical scheme in the embodiment of the present invention, it is clear that described embodiment is only The embodiment of a part of the invention, rather than whole embodiments.Based on the embodiment in the present invention, ordinary skill people The every other embodiment that member is obtained under the premise of creative work is not made, should all belong to the model of present invention protection Enclose.
It should be noted that term " first ", " in description and claims of this specification and above-mentioned accompanying drawing Two " it is etc. for distinguishing similar object, without for describing specific order or precedence.It should be appreciated that so using Data can exchange in the appropriate case, so as to embodiments of the invention described herein can with except illustrating herein or Order beyond those of description is implemented.Additionally, term " comprising " and " having " and their any deformation, it is intended that cover Lid is non-exclusive to be included, for example, the process, method, system, product or the equipment that contain series of steps or unit are not necessarily limited to Those steps or unit clearly listed, but may include not list clearly or for these processes, method, product Or other intrinsic steps of equipment or unit.
Embodiment 1
According to embodiments of the present invention, there is provided a kind of method of testing embodiment, it is necessary to explanation, in the flow chart of accompanying drawing The step of showing can perform in the such as one group computer system of computer executable instructions, and, although in flow chart In show logical order, but in some cases, shown or described step can be performed with different from order herein Suddenly.
Fig. 1 is a kind of method of testing flow chart according to embodiments of the present invention, as shown in figure 1, the method includes following step Suddenly:
Step S102, during test assignment is performed, obtains the abnormality that software to be tested occurs, wherein, Abnormality is the state in the range of presetting;
Step S104, obtains the situation that length occurs for the abnormality in the time period of scheduled duration, wherein, abnormal shape The situation that state occurs includes:The abnormality that software to be tested occurs in different test equipments;
Step S106, the stability of the assessment of scenario software to be tested occurred according at least to abnormality.
Used as a kind of optional embodiment, above-mentioned test assignment can be the stability for test software or software systems Task, the software or software systems of test can be, but not limited to operate in the intelligence such as computer, panel computer, notebook, mobile phone In energy equipment;Above-mentioned abnormality can be the state in state range set in advance, in a kind of optional implementation method, pin To different software or software systems, can be somebody's turn to do according to the operation platform where the software or software systems and application scenarios definition The abnormality of software or software systems, the phenomenon scope included to abnormality is defined, and the anomaly to occurring Demarcated.The situation that above-mentioned abnormality occurs can set including software or software systems to be tested in different testing results The abnormality occurred in standby (equipment for running the software or software systems).Based on skill disclosed in above-mentioned steps S102 to S106 Art scheme, during test assignment is performed, obtains the abnormality that software to be tested occurs, and in preset time period The situation that the abnormality occurs in different test equipments, and occurred in different test equipments according to these abnormalities Situation assesses the stability of software to be tested.
Herein it should be noted that being directed to certain a software or software systems, can be by the software or software systems can Energy abnormality is defined, and the phenomenon scope that these abnormalities are included is defined, and then abnormal existing to what is occurred As being demarcated.Easily it is noted that the phenomenon showed by the failure behaviour of software or software systems is a lot, as one kind Optional embodiment, can only choose serious failure behaviour as statistics.
Herein it should be noted that the length of time period can be the different cycles according to software development and be determined , or according to software postrun operation phase is issued to determine.Or, the length of time period can also be basis Performed test assignment determines, if what test assignment performed is use-case test, then now just can be according to use-case Content in test determines the length of the time period, if what is performed is free test, now the length of time period can be entered Row adjustment.
In a kind of optional embodiment, above-mentioned abnormality can be collect from multiple different operating systems (for example, Windows, iOS, Android etc.) abnormality, abnormality now can be used for characterizing of the software to be tested Overall situation, or can also differentiate operating system, can now obtain this in each operating system to be tested soft The abnormality of part.
From the foregoing, it will be observed that in the above embodiments of the present application, for certain a software or software systems, defining the software or soft The abnormality that part system is likely to occur, is defined to the phenomenon scope that these abnormalities are included, and the exception to occurring Phenomenon is demarcated;During test assignment is performed, it is retrieved as first in software to be tested state range set in advance At least one abnormality, and obtain the abnormality in preset time period different test equipments (operation software under testing Equipment) on occur situation, the stability of software to be tested is assessed according at least to the situation of the appearance of these abnormalities. By scheme disclosed in the present embodiment, the stable state of instant understanding software systems is reached, and it is timely according to the stable state The purpose of countermeasure is provided, it is achieved thereby that reducing user's loss, improving the technique effect of Consumer's Experience, and then is solved existing There is the technical problem for not having the measurement for software stability in technology.
In software or the different phase of the construction cycle of software systems, or when software or software systems are postrun different Between section, the abnormality occurred on the software or software systems may be different, therefore, it is possible to obtain software under testing or software systems The situation that abnormality in Preset Time goes out item carrys out the stability of the comprehensive descision software or software systems, optional in one kind Embodiment in, as shown in Fig. 2 according at least to abnormality occur assessment of scenario software to be tested stability, can wrap Include following steps:
Step S202, obtains the situation that the abnormality in adjacent multiple time periods occurs;
Step S204, situation about being occurred according to abnormality in adjacent multiple time periods determines becoming for abnormality appearance Gesture;
Step S206, according to the stability of trend evaluation software to be tested.
Specifically, in the above-described embodiments, it is the abnormality appearance in the time period of scheduled duration length is obtained After situation, the situation that the abnormality in adjacent multiple time periods occurs is obtained, and according in adjacent multiple time periods Abnormality occur situation determine software to be tested abnormality occur trend, assessed finally according to trend to be measured The stability of software.
It should be noted that during to software or software system test, it is public based on above-mentioned steps S202 to S206 The scheme opened, can assess according to a certain software or the software systems situation that all of abnormality occurs in Preset Time The stability of software under testing, rather than the frequency for relying solely on mistake or failure, or judges to be tested by empirical equation The stability of software or software systems.
By above-described embodiment, the steady of software under testing can be assessed according to the trend of the abnormality of software under testing appearance It is qualitative, improve the accuracy of assessment software stability.
Because the hardware configuration or operating system of each test equipment are different, same software or software systems are arranged on difference Test equipment on its stability it is not necessarily identical, in an alternative embodiment, as shown in figure 3, according at least to exception The stability of the assessment of scenario software to be tested that state occurs may include steps of:
Step S302, the number of times that the quantity and/or abnormality of the test equipment appeared according to abnormality occur is commented Estimate the stability of software to be tested.
Specifically, in the above-described embodiments, above-mentioned test equipment can be currently installed at least one of software to be tested and set It is standby;It is a kind of in situation about being occurred according to the abnormality of equipment to be tested during the stability of software to be tested is assessed In optional implementation method, the abnormality that can obtain software to be tested or software systems goes out at least one test equipment Existing number of times assesses the stability of software under testing;In another optional implementation method, can also obtain and abnormality occur Test equipment quantity, it is preferable that different operating system (for example, Windows, iOS, Android etc.) or not can be counted The quantity of the test equipment of same type (for example, computer, panel computer, notebook, mobile phone etc.) come assess software to be tested or The stability of software systems.As one kind preferred embodiment, above two implementation method can be combined, i.e., according to abnormal shape The number of times that the quantity and abnormality of the test equipment that state is appeared in occur assesses the stability of software to be tested.
It should be noted that the result of stability can be described using natural language, natural language description is used Stability result user can be made to be more prone to understand the state of the software to be tested or software systems.
By above-described embodiment, it may be considered that install the factor of the hardware device of software under testing or software systems, it is to avoid The reason for test equipment itself, causes the erroneous judgement to software or software systems on the measurement equipment, improves assessment soft The accuracy of part stability.
Based on above-described embodiment, in a kind of optional embodiment, as shown in figure 4, the survey appeared according to abnormality The number of times that the quantity and/or abnormality of examination equipment occur assesses the stability of software to be tested, may include steps of:
Step S402, the number of times in-scope that quantity and/or abnormality according to test equipment occur determines to be tested The stability of software, wherein, scope is set in advance.
In a kind of optional embodiment, above range can exception occur according to the same type software of software to be tested What the situation of state determined.
Specifically, above-mentioned same type software can be and software under testing function or type of service identical other software; Can be with other versions of test software to be measured, including stable version and non-stable version.Specifically, opened in the whole of software In the hair cycle, can be surveyed from the version of software to be tested and after preliminarily stabilised, just start statistics.Wherein, when version is unstable The data of statistics, can be not only used for measuring the instant stability status of product, be also used for characterizing development ability and level;And cut Data after the version stabilization got, can be used for assessing the stability after product issue.
As one kind preferred embodiment, Fig. 5 is a kind of preferred method of testing flow according to embodiments of the present invention Figure, as shown in figure 5, the method for testing may include steps of:
Step S502, defines stability and scope.
Specifically, in above-mentioned steps, a specific software systems definition of stability is provided, summarizes software or soft to be tested Part system may bring the anomaly of loss to user.The phenomenon scope that these abnormalities are included is defined, to going out Existing image is demarcated.It is determined that occurring an anomaly in software running process, count 1 time.
Step S504, determines linear module.
Specifically, in above-mentioned steps, determine measure scales, that is, define the unit of measurement, such as duration (when, day etc.); And for example people, platform etc..
Step S506, determines Test Strategy and plan.
Specifically, in above-mentioned steps, Test Strategy and plan in the software version cycle are formulated.
Step S508, performs test.
Specifically, in above-mentioned steps, according to Test Strategy and tester in the construction cycle of software or running Draw, perform test, test can be use-case test, freely test.Test case includes to basic function, user's flow, uses Family scrnario testing, it might even be possible to the system testing including the test that user participates in etc..
Step S510, recording exceptional number of times.
Specifically, in above-mentioned steps, frequency of abnormity in record measure scales section.According to the measure scales segment record for determining The number of times of anomaly is produced, frequency of abnormity, people's number of times or the platform number of times for occurring is counted.
Step S512, calculates exceptional value.
Specifically, in above-mentioned steps, frequency of abnormity and measure scales section are carried out into ratio, draws software under testing or software The instant exceptional value of system, the exceptional value can be used for characterizing the stability of software to be tested.In a kind of optional implementation method, The frequency of abnormity occurred in one section of scale, abnormal people's number of times or platform number of times and measure scales section are compared, the ratio that will be drawn Value is defined as an index or parameter, characterizes the stability value of specific scale section, identifies the instant stability data of software systems.
Step S514, judges whether to complete.
Specifically, in above-mentioned steps, continuance test and record in software development cycle or run time section, and judge Test whether to complete, if completed, perform step S516;Conversely, then performing step S508.
Step S516, data statistic analysis.
Specifically, in above-mentioned steps, interception record segment is counted, for example, average etc., show that software systems are overall steady Qualitative parameter.After these data values of statistics a period of time, the stability data to counting carries out trend analysis, forecasting software Stability of a system trend, so as to obtain the stability data of software to be tested or software systems.
Based on scheme disclosed in above-mentioned steps S512 to S516, there is provided a kind of stability metric system, by the stabilization Property gauging system, can immediately understand the stable state of software systems, exploitation analysis in time speculates that user is likely to occur probability simultaneously There is provided countermeasure, it is to avoid cause user to lose.
It should be noted that the present embodiment internally software systems product such as CAXA, entity design, coordinated management In be applied and verify, by defining (including the abnormality and be this of the stability data in each release cycle The scope that the phenomenon that a little abnormalities are included is demarcated), in the test process of software product, it is analyzed and tests from exploitation visual angle Card, finally, user feedback and system the result after product issue can coincide substantially.
Embodiment 2
According to embodiments of the present invention, a kind of device embodiment for realizing above-mentioned method of testing is additionally provided, Fig. 6 is root According to a kind of test device schematic diagram of inventive embodiments, such as Fig. 6 shows that the device includes:First acquisition unit 601, second is obtained Unit 603 and assessment unit 605.
Wherein, first acquisition unit 601, are occurred for during test assignment is performed, obtaining software to be tested Abnormality, wherein, abnormality is the state in the range of presetting;
Second acquisition unit 603, for obtaining the situation that the abnormality in the time period that length is scheduled duration occurs, Wherein, the situation that abnormality occurs includes:The abnormality that software to be tested occurs in different test equipments;
Assessment unit 605, the stability of the assessment of scenario software to be tested for occurring according at least to abnormality.
Herein it should be noted that above-mentioned first acquisition unit 601, second acquisition unit 603 and the correspondence of assessment unit 605 Step S102 to S106 in embodiment 1, said units are identical with example and application scenarios that the step of correspondence is realized, but It is not limited to the disclosure of that of above-described embodiment 1.It should be noted that said units can be as a part of of device Performed in the such as one group computer system of computer executable instructions.
In a kind of optional embodiment, above-mentioned assessment unit 605 can include:First acquisition module, for obtaining phase The situation that abnormality in adjacent multiple time periods occurs;Second acquisition module, for according in adjacent multiple time periods The situation that abnormality occurs determines the trend that abnormality occurs;Evaluation module, for according to trend evaluation software to be tested Stability.
Herein it should be noted that above-mentioned first acquisition module, the second acquisition module and evaluation module correspond to embodiment 1 In step S202 to S206, above-mentioned module is identical with the example realized of step and application scenarios of correspondence, but is not limited to State the disclosure of that of embodiment 1.It should be noted that above-mentioned module can be in such as one group calculating as a part of of device Performed in the computer system of machine executable instruction.
In a kind of optional embodiment, the test that above-mentioned assessment unit can be also used for being appeared according to abnormality sets The number of times that standby quantity and/or abnormality occur assesses the stability of software to be tested.
In a kind of optional embodiment, above-mentioned assessment unit can be also used for according to quantity and/or number of times in-scope Determine the stability of software to be tested, wherein, scope is set in advance.
In a kind of optional embodiment, above range is that abnormality occur according to the same type software of software to be tested Situation determine.
The embodiments of the present invention are for illustration only, and the quality of embodiment is not represented.
In the above embodiment of the present invention, the description to each embodiment all emphasizes particularly on different fields, and does not have in certain embodiment The part of detailed description, may refer to the associated description of other embodiment.
In several embodiments provided herein, it should be understood that disclosed technology contents, can be by other Mode is realized.Wherein, device embodiment described above is only schematical, such as division of described unit, Ke Yiwei A kind of division of logic function, can there is other dividing mode when actually realizing, such as multiple units or component can combine or Person is desirably integrated into another system, or some features can be ignored, or does not perform.Another, shown or discussed is mutual Between coupling or direct-coupling or communication connection can be the INDIRECT COUPLING or communication link of unit or module by some interfaces Connect, can be electrical or other forms.
The unit that is illustrated as separating component can be or may not be it is physically separate, it is aobvious as unit The part for showing can be or may not be physical location, you can with positioned at a place, or can also be distributed to multiple On unit.Some or all of unit therein can be according to the actual needs selected to realize the purpose of this embodiment scheme.
In addition, during each functional unit in each embodiment of the invention can be integrated in a processing unit, it is also possible to It is that unit is individually physically present, it is also possible to which two or more units are integrated in a unit.Above-mentioned integrated list Unit can both be realized in the form of hardware, it would however also be possible to employ the form of SFU software functional unit is realized.
If the integrated unit is to realize in the form of SFU software functional unit and as independent production marketing or use When, can store in a computer read/write memory medium.Based on such understanding, technical scheme is substantially The part for being contributed to prior art in other words or all or part of the technical scheme can be in the form of software products Embody, the computer software product is stored in a storage medium, including some instructions are used to so that a computer Equipment (can be personal computer, server or network equipment etc.) perform each embodiment methods described of the invention whole or Part steps.And foregoing storage medium includes:USB flash disk, read-only storage (ROM, Read-Only Memory), arbitrary access are deposited Reservoir (RAM, Random Access Memory), mobile hard disk, magnetic disc or CD etc. are various can be with store program codes Medium.
The above is only the preferred embodiment of the present invention, it is noted that for the ordinary skill people of the art For member, under the premise without departing from the principles of the invention, some improvements and modifications can also be made, these improvements and modifications also should It is considered as protection scope of the present invention.

Claims (10)

1. a kind of method of testing, it is characterised in that including:
During test assignment is performed, the abnormality that software to be tested occurs is obtained, wherein, the abnormality is State in the range of presetting;
The situation that length occurs for the abnormality in the time period of scheduled duration is obtained, wherein, the abnormality goes out Existing situation includes:The abnormality that the software to be tested occurs in different test equipments;
The stability of software to be tested described in the assessment of scenario occurred according at least to the abnormality.
2. method according to claim 1, it is characterised in that according at least to the assessment of scenario institute that the abnormality occurs The stability for stating software to be tested includes:
Obtain the situation that the abnormality in adjacent multiple time periods occurs;
Situation about being occurred according to the abnormality in adjacent multiple time periods determines becoming for the abnormality appearance Gesture;
The stability of software to be tested according to the trend evaluation.
3. method according to claim 1, it is characterised in that according at least to the assessment of scenario institute that the abnormality occurs The stability for stating software to be tested includes:
Described in the number of times assessment that the quantity of the test equipment appeared according to the abnormality and/or the abnormality occur The stability of software to be tested.
4. method according to claim 3, it is characterised in that the number of the test equipment appeared according to the abnormality The stability that the number of times that amount and/or the abnormality occur assesses the software to be tested includes:
The stability of the software to be tested is determined according to the quantity and/or the number of times in-scope, wherein, the scope For set in advance.
5. method according to claim 4, it is characterised in that the scope is the same type according to the software to be tested What the situation that the abnormality occurs in software determined.
6. a kind of test device, it is characterised in that including:
First acquisition unit, for during test assignment is performed, obtaining the abnormality that software to be tested occurs, its In, the abnormality is the state in the range of presetting;
Second acquisition unit, for obtaining the situation that the abnormality in the time period that length is scheduled duration occurs, its In, the situation that the abnormality occurs includes:The described abnormal shape that the software to be tested occurs in different test equipments State;
Assessment unit, for the stability of software to be tested described in the assessment of scenario that occurs according at least to the abnormality.
7. device according to claim 6, it is characterised in that the assessment unit includes:
First acquisition module, the situation for obtaining the appearance of the abnormality in adjacent multiple time periods;
Second acquisition module, described in being determined according to the situation of the abnormality appearance in adjacent multiple time periods The trend that abnormality occurs;
Evaluation module, for the stability of the software to be tested according to the trend evaluation.
8. device according to claim 6, it is characterised in that the assessment unit is used to being occurred according to the abnormality Test equipment quantity and/or the number of times that occurs of the abnormality assess the stability of the software to be tested.
9. device according to claim 8, it is characterised in that the assessment unit is used for according to the quantity and/or institute The stability that number of times in-scope determines the software to be tested is stated, wherein, the scope is set in advance.
10. device according to claim 9, it is characterised in that the scope is according to the similar of the software to be tested What the situation that the abnormality occurs in type software determined.
CN201710079041.8A 2017-02-14 2017-02-14 Method of testing and device Pending CN106874201A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710079041.8A CN106874201A (en) 2017-02-14 2017-02-14 Method of testing and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710079041.8A CN106874201A (en) 2017-02-14 2017-02-14 Method of testing and device

Publications (1)

Publication Number Publication Date
CN106874201A true CN106874201A (en) 2017-06-20

Family

ID=59166260

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710079041.8A Pending CN106874201A (en) 2017-02-14 2017-02-14 Method of testing and device

Country Status (1)

Country Link
CN (1) CN106874201A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109426605A (en) * 2017-08-23 2019-03-05 龙芯中科技术有限公司 The stability test method and apparatus of computer
CN115576857A (en) * 2022-12-08 2023-01-06 大方智造(天津)科技有限公司 Automatic testing method based on CAM testing engine

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777022A (en) * 2010-03-03 2010-07-14 中科华核电技术研究院有限公司 Method for analyzing software reliability and system thereof
CN102708050A (en) * 2012-04-21 2012-10-03 北京迈凯互动网络科技有限公司 Method and system for testing mobile application
CN104156312A (en) * 2014-08-11 2014-11-19 浪潮(北京)电子信息产业有限公司 Method for evaluating software reliability
US20160041892A1 (en) * 2013-09-27 2016-02-11 Emc Corporation System for discovering bugs using interval algebra query language

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101777022A (en) * 2010-03-03 2010-07-14 中科华核电技术研究院有限公司 Method for analyzing software reliability and system thereof
CN102708050A (en) * 2012-04-21 2012-10-03 北京迈凯互动网络科技有限公司 Method and system for testing mobile application
US20160041892A1 (en) * 2013-09-27 2016-02-11 Emc Corporation System for discovering bugs using interval algebra query language
CN104156312A (en) * 2014-08-11 2014-11-19 浪潮(北京)电子信息产业有限公司 Method for evaluating software reliability

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
翁秀木: ""一个通用的软件质量评估指标体系"", 《软件》 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109426605A (en) * 2017-08-23 2019-03-05 龙芯中科技术有限公司 The stability test method and apparatus of computer
CN115576857A (en) * 2022-12-08 2023-01-06 大方智造(天津)科技有限公司 Automatic testing method based on CAM testing engine

Similar Documents

Publication Publication Date Title
US20210319375A1 (en) Churn prediction in a broadband network
US11669420B2 (en) Monitoring performance of computing systems
Ehlers et al. Self-adaptive software system monitoring for performance anomaly localization
US8260622B2 (en) Compliant-based service level objectives
US20150371163A1 (en) Churn prediction in a broadband network
CN108463973A (en) Fingerprint recognition basic reason is analyzed in cellular system
US20150067153A1 (en) Remote monitoring of data facility in real-time using wireless sensor network
US20160132798A1 (en) Service-level agreement analysis
CN112148586A (en) Machine-assisted quality assurance and software improvement
CN105721187A (en) Service fault diagnosis method and apparatus
US8832839B2 (en) Assessing system performance impact of security attacks
CN109992473B (en) Application system monitoring method, device, equipment and storage medium
CN109495291B (en) Calling abnormity positioning method and device and server
US10558206B2 (en) Electrical device degradation determination
US20220214957A1 (en) Machine learning models applied to interaction data for facilitating modifications to online environments
US20190354913A1 (en) Method and system for quantifying quality of customer experience (cx) of an application
CN106021054A (en) Method and apparatus for testing upgrading and downgrading stability of BMC
CN105429792A (en) User behavior flow obtaining method and device and user behavior analysis method and system
CN106874201A (en) Method of testing and device
CN107679423A (en) Partition integrity inspection method and device
CN107317708A (en) The monitoring method and device of a kind of Court business application system
CN109064211A (en) Sales service data analysing method, device and server
Jain et al. Software reliability growth model (SRGM) with imperfect debugging, fault reduction factor and multiple change-point
US20160182333A1 (en) Measuring affinity bands for pro-active performance management
Bayram et al. Improving reliability with dynamic syndrome allocation in intelligent software defined data centers

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20170620