CN100543701C - A kind of method and system that realize embedded software unconventionality testing - Google Patents

A kind of method and system that realize embedded software unconventionality testing Download PDF

Info

Publication number
CN100543701C
CN100543701C CNB2007103023715A CN200710302371A CN100543701C CN 100543701 C CN100543701 C CN 100543701C CN B2007103023715 A CNB2007103023715 A CN B2007103023715A CN 200710302371 A CN200710302371 A CN 200710302371A CN 100543701 C CN100543701 C CN 100543701C
Authority
CN
China
Prior art keywords
abnormality test
abnormality
script
software
testing
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.)
Expired - Fee Related
Application number
CNB2007103023715A
Other languages
Chinese (zh)
Other versions
CN101183335A (en
Inventor
左军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CNB2007103023715A priority Critical patent/CN100543701C/en
Publication of CN101183335A publication Critical patent/CN101183335A/en
Application granted granted Critical
Publication of CN100543701C publication Critical patent/CN100543701C/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Landscapes

  • Debugging And Monitoring (AREA)

Abstract

The present invention relates to a kind of method that realizes embedded software unconventionality testing, comprising: step 1 is provided with the abnormality test rules; Step 2 is inserted the abnormality test point according to the abnormality test rules in software source code; Step 3 is carried out writing or revising of abnormality test script according to the abnormality test rules, is used to generate exception condition; Step 4 makes up running environment and downloads the abnormality test script; Step 5 starts testing process and carries out abnormality test, and operation is put corresponding abnormality test script with abnormality test, according to the result of abnormal behaviour the software anomaly processing power is judged.The present invention is by embedding script in source code, the processing that needs are changed changes script control over to, based on the convenient feature of script to data and flow operations, improved the dirigibility that exception condition changes, can adjust corresponding unusual value or unusual flow process by changing content for script at the abnormity point place, reach the test of various abort branches.

Description

A kind of method and system that realize embedded software unconventionality testing
Technical field
The present invention relates to the embedded software test field, relate in particular to a kind of method and system that realize embedded software unconventionality testing.
Background technology
Embedded software system is owing to be subjected to the restriction of development environment, and along with the expansion of object scale, from the unit, the difficulty that is integrated into system also continues to increase, the abnormality test content is difficult to carry out more aspect software test.Especially signaling control stream is the key of building the miscellaneous service flow process in embedded system, belongs to nervous system, just seems especially important at the abnormality processing of signaling, and corresponding abnormality test must be implemented, but more limited on means of testing.
Software processes be divided into unusual flow process and unusual value unusually, the former produces other branch process for not walking original flow process; Unusual value is then walked original flow process, but the data value is changed.
Traditional software unconventionality testing is the simplest to be that manual systems produces unusual excitation, and this mode can only cause the exception condition of simple minority, as unusual flow process, can not satisfy test request; Other mode is exactly directly to revise source program, write the code of ANOMALOUS VARIATIONS therein, walk then when flow process and just produce exception condition by the code requirement, this mode can enlarge unusual covering, but belong to " hard coded " type, revise code compilation run again when needing the conversion condition again, very loaded down with trivial details, the influence to source program is bigger simultaneously, can only use as interim debugging, will do shielding after test is finished, test code is messy, is difficult to management.Generally speaking, existing software unconventionality testing manner of execution very flexible in test process, efficient is low.
Summary of the invention
In order to solve above-mentioned technical matters, a kind of method that realizes embedded software unconventionality testing is provided, its purpose is, overcomes the shortcoming of prior art underaction and inefficiency when carrying out software unconventionality testing.
The invention provides a kind of method that realizes embedded software unconventionality testing, comprising:
Step 1 is provided with the abnormality test rules;
Step 2 finds the position that produces exception condition in the software source code according to the abnormality test rules in software source code, come consolidation abnormality test point by the primary data information (pdi) that exception condition depended on, and inserts the abnormality test point, and it is grand promptly to insert abnormality processing;
Step 3 is carried out writing or revising of abnormality test script according to the abnormality test rules, and abnormity point of living in is carried out unusual flow process/unusual value, is used to generate exception condition;
Step 4 makes up running environment, customizes the abnormality test script corresponding with abnormality test point, the abnormality test script that is customized is generated the abnormality test use-case, and download in the running environment;
Step 5, start testing process and carry out abnormality test, operation comprises the software source code of abnormality test point, if run to abnormality test point place satisfy condition move with abnormality test put corresponding abnormality test script, produce abnormal behaviour, and the software anomaly processing power is judged according to the result of abnormal behaviour.
Further, the grand data message that comprises message format of described abnormality processing.
Step 2 also comprises step 203, handles for the situation of returning after the abnormality processing; Described return situation comprise continue after abnormality processing is finished the follow-up flow process of source program, directly withdraw from this scheduling or skip the follow-up one section code of source program after continue to carry out.
Step 3 comprises:
Step 401 is selected corresponding abnormality test point according to the abnormality test rules, with the grand data message of bringing into form of message of described abnormality processing as input parameter;
Step 402, if carry out unusual flow processing, then the abnormality test script sends message according to input parameter; Handle if carry out unusual value, then the abnormality test script is revised the value of input parameter.
Step 3 also comprises: in real time manual or revise the abnormality test script automatically.
Step 4 comprises:
Step 5 comprises:
Step 501 starts testing process, and operation comprises the software source code of abnormality test point;
Step 502, software source code are judged by abnormality processing is grand carrying out abnormality test point place, if abnormality test point has customized the abnormality test script, are then changed the abnormality test script over to and handle, execution in step 503;
Step 503, the abnormality test script carries out unusual flow processing or unusual value according to described data message, generates exception condition;
Step 504 is synchronized to actual data area with the exception condition that is generated, and is used for tested software and produces abnormal behaviour, according to the result of abnormal behaviour the software anomaly processing power is judged.
The invention provides a kind of system that realizes embedded software unconventionality testing, comprising:
Abnormality test point insert module 101, be used for finding the position that produces exception condition in the software source code at software source code according to the abnormality test rules, come consolidation abnormality test point by the primary data information (pdi) that exception condition depended on, and the abnormality test point is inserted in the relevant position in software source code;
Abnormality test script editor module 102 is used for carrying out writing or revising of abnormality test script according to the abnormality test rules, abnormity point of living in is carried out unusual flow process/unusual value, to generate exception condition;
Abnormality test script download module 103 is used to make up running environment, customizes the abnormality test script corresponding with abnormality test point, and the abnormality test script that is customized is generated the abnormality test use-case, and the downloading-running environment;
Abnormality test execution module 104, be used to start testing process and carry out abnormality test, operation comprises the software source code of abnormality test point, if run to abnormality test point place satisfy condition move with abnormality test put corresponding abnormality test script, make tested software produce abnormal behaviour, and the software anomaly processing power is judged according to the result of abnormal behaviour.
Abnormality test point insert module also is used for the situation of returning after the abnormality processing is handled; Described return situation comprise continue after abnormality processing is finished the follow-up flow process of source program, directly withdraw from this scheduling or skip the follow-up one section code of source program after continue to carry out.
Abnormality test point insert module, it is grand also to be used for inserting abnormality processing at source code, the grand data message that comprises message format of abnormality processing.
Abnormality test script editor module also is used for for the test script that has write, but according to the needs real time modifying scripted code in when operation, does abnormality processing by new unusual formation condition, the different abnormal conditions of test same position.
The present invention is by embedding script in source code, the processing that needs are changed changes script control over to, based on the convenient feature of script to data and flow operations, improved the dirigibility that exception condition changes, can adjust corresponding unusual value or unusual flow process by changing content for script at the abnormity point place, reach the test of various abort branches.Script does not need and source program compilation run together, revises synchronously at any time and downloads, and has improved abnormality test and has carried out efficient.Produce and to be used for testing own code stabilizing power unusually, also can provide unusual interactive testing the other side stabilizing power for tested side.On using except can be in the unit/integrated/system's stage carries out the abnormality test, can also carry out the flow process self-test with the script emulation environment in the unit testing stage.The exceptional instructions that both insert in own code is consistent, is corresponding test script difference.In specific implementation, form was all unified when various types of ANOMALOUS VARIATIONS were inserted abnormity point in source program, and just a function is grand, be empty getting final product with macro definition when at non-test pattern, to source code influence drop to minimum.Each unusual test script is preserved with document form, can be together related with the abnormality test rules, be convenient to management.
Description of drawings
Fig. 1 is the system construction drawing of abnormality test pattern;
Fig. 2 is the process flow diagram of abnormality test method;
Fig. 3 returns the process flow diagram that the source program different situations are handled after the abnormality processing;
Fig. 4 is the test script working mechanism explanation of being adopted in the abnormality test method.
Embodiment
Abnormality test method provided by the invention comprises as shown in Figure 2:
The first step, carry out abnormality test rules designs, this is the prerequisite of customization abnormality processing content, belongs to the category of use-case design, is the preliminary work of this abnormality test method;
Second the step, in source code, insert the abnormality test point according to the abnormality test rules, this is a key point of this abnormality test method, a tie that belongs to source code and test script, the requirement of reflection test procedure, in commission realize changing unusual flow process over to, return to former flow process after finishing dealing with again from former flow process;
The 3rd step, carry out writing/revising of abnormality test script according to the abnormality test rules, content for script directly embodies the rules requirement, and abnormity point of living in is carried out the value of unusual flow process/unusually, is used for the generation of exception condition;
The 4th goes on foot, carries out running environment structure and test script download, to have the software version and the normally operation in embedded environment of abnormality test module of abnormality test point, select corresponding abnormality test script according to content measurement, download to from the backstage (foreground embedded device) the running environment.
The 5th step, start testing process and carries out abnormality test, satisfy condition then change script over to and handle, produce required exception condition, change the follow-up operation of source program if tested software is gone to the abnormity point place in operational process.After this step is finished, also can carry out for the 3rd step, script is adjusted in craft or robotization.
The 6th step, draw the abnormality test conclusion, judge the quality of tested software for abnormality processing according to the output information of final testing result and abnormality test implementation.
Above-mentioned second step can comprise again:
21), find generation exception condition position in the source code according to the requirement of abnormality test rules, come consolidation abnormality test point by the primary data information (pdi) that exception condition depended on, might a plurality of different exception conditions be to form promptly at same primary data information (pdi), and, then can be summed up as an abnormality test point in identical flow process position.
22), after consolidation finishes abnormality test point, insert abnormality processing in the source code relevant position grand, bring into the form of message to comprise the data message that produces exception condition, as message name, message data.
23), return situation for difference after the abnormality processing and handle, a kind of is to continue the follow-up flow process of source program after abnormality processing is finished, a kind of is directly to withdraw from this scheduling, a kind of is to continue to carry out after skipping the follow-up one section code of source program.
Above-mentioned the 3rd step can comprise again:
31), select corresponding abnormality test point, the grand data of bringing into form of message of abnormality processing are used for the script abnormality processing as input parameter (ginseng gone in abbreviation) according to the requirement of abnormality test rules.
32), carry out unusual flow processing, will send corresponding message by script, will comprise this message data in the script, and send instruction by script and realize sending according to the designing requirement of abnormality test rules for needs.
33), carry out unusual value for needs and handle, the message data content that is about to import into changes, and directly by the script data assign operation data content is customized, thereby forms improper value condition.
The abnormal data of unusual herein value correspondence is divided into unexpected message and unusual variable, wherein wants the message of ANOMALOUS VARIATIONS to be meant the system-level definition of whole test product, and variable then is a local definition, as certain functional module/code file local variable.Unexpected message is owing to be unified Definition in system, as message name and message body correspondence, can on script mechanism, direct correlation handle, then to do further variation at local variable, disposal route is to list to need the argument table controlled in this functional module/code file, is defined as a unified UNION structure as this unusual variable message body, the more corresponding unusual variable message of definition, form visual fixed correlation relation of seeing in the pathological system, handle for script.
34), for the test script that has write, but according to the needs real time modifying scripted code in when operation, do abnormality processing by new unusual formation condition, the different abnormal conditions of test same position.
Above-mentioned the 4th step can comprise again:
41), make up the embedded software system environment, will have the software version and the normally startup on the operation embedded device of abnormality test module of abnormality test point.
42), select to want the abnormality test point of test execution, customize corresponding abnormality processing script, content can be script or the modification targetedly on demand thereon that abovementioned steps has been kept; The abnormality test that has customized the abnormality processing script is named a person for a particular job then processed at running software.
43), will customize good whole scripts and gather and generate the abnormality test use-case that is used to carry out, download to (foreground embedded device) in the embedded running environment by the backstage.
Above-mentioned the 5th step can comprise again:
51), start testing process, allow software be moved.
52), software code goes to abnormality test point place in the process of implementation and made a decision by the grand respective function of abnormality processing, handle if satisfy condition then change script over to; Whether Rule of judgment is for having customized the abnormality processing script to this abnormality test point.
53), when changing script over to and handling, the grand data that comprise information of bringing into of abnormality processing comprise message name, message content etc., these data are copied in the script executing body requirement by scripted code and handle, as unusual flow process/unusual value.
54), abnormality processing finish after these data be synchronized to actual data area again, use for later code, produce the needed abnormal behaviour of this abnormality test rules.
Among Fig. 2,, can download different test scripts and produce corresponding exception condition along with the difference of abnormality test rules content measurement.This can have dual mode to select, and a kind of is the manual test script content of revising at any time as required, downloads the back and forms new abnormality processing condition, is applicable to the on-the-spot spread scenarios of abnormality test; Another kind of mode is the robotization mode, different test scripts are write in i.e. generation of putting various exception conditions at certain abnormality test, not downloading respectively in the homogeneous loop test, form different exception conditions and test automatically, this is applicable to the customization test of promptly deciding exception condition.
Fig. 1 is the system construction drawing of abnormality test pattern, and script editor/communication interface part is divided into background program and operates on the PC among the figure, is used for the edit script use-case, and the control downloading-running shows operation information; Other parts as front stage operation on embedded system device, measurand resides on the operating system supporting layer as business process, assisted process and script executing process are that abnormality test joins the extention in the system of measurand place, are used to receive Download Script and actual the execution; Handling function AbProc is an overall situation function, may be defined as that abnormality processing is grand to be called for measurand, realizes in the normal code processing procedure insertion to unusual script.Assisted process, script executing process and handling function unification can be called the abnormality test module.
It can be divided into several functional modules according to the System Operation function, wherein function AbProc and the grand measurand 1 of adding abnormality test have constituted abnormality test point insert module 101, are used for inserting the abnormality test point according to the abnormality test rules at software source code; The script edit segment has constituted abnormality test script editor module 102, is used for carrying out writing or revising of abnormality test script according to the abnormality test rules, to generate exception condition; The foreground assisted process has partly constituted abnormality test script download module 103 in conjunction with the backstage downloading control, is used to make up running environment and downloads the abnormality test script; The script executing process that has the directive script district has constituted abnormality test execution module 104, imports data message into by the ginseng of going into of function AbProc, and finishes the generation of exception condition according to directive script.
Measurand is divided into two classes according to the test process difference, and a class is that measurand 1 is tested oneself, and another kind of the generation by measurand 1 tested measurand 2 unusually.Measurand 1 is all moved the abnormity point of oneself inserting under two kinds of situations, and measurand 2 is not then inserted abnormity point, any change that it goes without doing.
Fig. 3 returns the process flow diagram that the source program different situations are handled after the abnormality processing.In at the exception handling procedure that certain abnormality test point carried out, consider the different situations of returning source program after script is finished, comprise three kinds: a kind of is to continue the follow-up flow process of source program after abnormality processing is finished, a kind of is directly to withdraw from this scheduling, and a kind of is to continue to carry out after skipping the follow-up one section code of source program.These several situations are all discerned by a Data Identification is set in the abnormality test script, and preceding two kinds are directly utilized abnormality processing grand, and the back is a kind of realizes by increasing the grand line identifier of bringing required redirect source code into of a unusual redirect in the grand back of abnormality test.Promptly when sign is set to 0, walk first kind of flow process, do not do extra process, abnormality processing function is directly returned, and program continues execute exception test point later code; When sign is set to 1, walk second kind of flow process, sign is reset to 0, in abnormality processing function, call the system function that withdraws from this scheduled for executing then, because handle function and still belong to this scheduling scope of tested process this moment, so will directly withdraw from this scheduling, the follow-up code of source program is no longer carried out; When sign is set to 2, walk the third flow process, the grand back of abnormality processing will design that to insert unusual redirect grand in this moment source code, go into ginseng for jumping to the line identifier of the follow-up code of source program, at first abnormality processing function is normally returned, it is grand that program enters unusual redirect, and it earlier is reset to 0 with sign, is exactly then to continue to carry out by one section code after calling " goto line identifier " and realizing skipping source program.
The test script working mechanism that Fig. 4 is in this method and is adopted illustrates, comprises the static state editor and two stages of dynamic operation of script.At first be based on the message structure information extraction of source program code, promptly in the script handled object all based on message and corresponding data structure.Go out the message structure that will use according to the abnormality test content choice, with the form generation use-case static zones of tabulation, promptly script data is described the zone.The logic step of processing described in user's various operation primitive of using script to provide then, generates the use-case dynamic area with the form of text, and promptly operation logic is described the zone.Two area contents unifications are kept in the text, generate test case file, so far finish static editing process.When next needing the actual motion use-case, script is handled kernel and is read in the use-case file, generate binary message in the internal memory by resolving to transform, by the data download process these information transmission are arrived foreground script executing body then, in the script executing body, start the use-case operation at last, the data of importing into according to the abnormality test point that will carry out are carried out corresponding script and are handled, and up to withdrawing from use-case, thereby finish the dynamic operation stage.
Those skilled in the art can also carry out various modifications to above content under the condition that does not break away from the definite the spirit and scope of the present invention of claims.Therefore scope of the present invention is not limited in above explanation, but determine by the scope of claims.

Claims (10)

1. a method that realizes embedded software unconventionality testing is characterized in that, comprising:
Step 1 is provided with the abnormality test rules;
Step 2, find the position that produces exception condition in the software source code according to the abnormality test rules, come consolidation abnormality test point by the primary data information (pdi) that exception condition depended on, and the abnormality test point is inserted in the relevant position in software source code, it is grand promptly to insert abnormality processing;
Step 3 is carried out writing or revising of abnormality test script according to the abnormality test rules, and abnormity point of living in is carried out unusual flow process/unusual value, is used to generate exception condition;
Step 4 makes up running environment, customizes the abnormality test script corresponding with abnormality test point, the abnormality test script that is customized is generated the abnormality test use-case, and download in the running environment;
Step 5, start testing process and carry out abnormality test, operation comprises the software source code of abnormality test point, if run to abnormality test point place satisfy condition move with abnormality test put corresponding abnormality test script, produce abnormal behaviour, and the software anomaly processing power is judged according to the result of abnormal behaviour.
2. the method for realization embedded software unconventionality testing as claimed in claim 1 is characterized in that, the grand data message that comprises message format of described abnormality processing.
3. the method for realization embedded software unconventionality testing as claimed in claim 1 is characterized in that, step 2 also comprises step 203, handles for the situation of returning after the abnormality processing; Described return situation comprise continue after abnormality processing is finished the follow-up flow process of source program, directly withdraw from this scheduling or skip the follow-up one section code of source program after continue to carry out.
4. the method for realization embedded software unconventionality testing as claimed in claim 1 or 2 is characterized in that, step 3 comprises:
Step 401 is selected corresponding abnormality test point according to the abnormality test rules, with the grand data message of bringing into form of message of described abnormality processing as input parameter;
Step 402, if carry out unusual flow processing, then the abnormality test script sends message according to input parameter; Handle if carry out unusual value, then the abnormality test script is revised the value of input parameter.
5. the method for realization embedded software unconventionality testing as claimed in claim 4 is characterized in that, step 3 also comprises: in real time manual or revise the abnormality test script automatically.
6. the method for realization embedded software unconventionality testing as claimed in claim 1 is characterized in that, step 5 comprises:
Step 501 starts testing process, and operation comprises the software source code of abnormality test point;
Step 502, software source code are judged by abnormality processing is grand carrying out abnormality test point place, if abnormality test point has customized the abnormality test script, are then changed the abnormality test script over to and handle, execution in step 503;
Step 503, the abnormality test script carries out unusual flow processing or unusual value according to described data message, generates exception condition;
Step 504 is synchronized to actual data area with the exception condition that is generated, and is used to produce abnormal behaviour, according to the result of abnormal behaviour the software anomaly processing power is judged.
7. a system that realizes embedded software unconventionality testing is characterized in that, comprising:
Abnormality test point insert module, be used for finding the position that produces exception condition in the software source code at software source code according to the abnormality test rules, come consolidation abnormality test point by the primary data information (pdi) that exception condition depended on, and the abnormality test point is inserted in the relevant position in software source code;
Abnormality test script editor module is used for carrying out writing or revising of abnormality test script according to the abnormality test rules, abnormity point of living in is carried out unusual flow process/unusual value, to generate exception condition;
Abnormality test script download module is used to make up running environment, customizes the abnormality test script corresponding with abnormality test point, the abnormality test script that is customized is generated the abnormality test use-case, and download to running environment;
The abnormality test execution module, be used to start testing process and carry out abnormality test, operation comprises the software source code of abnormality test point, if run to abnormality test point place satisfy condition move with abnormality test put corresponding abnormality test script, make tested software produce abnormal behaviour, and the software anomaly processing power is judged according to the result of abnormal behaviour.
8. the system of realization embedded software unconventionality testing as claimed in claim 7 is characterized in that,
Abnormality test point insert module also is used for the situation of returning after the abnormality processing is handled; Described return situation comprise continue after abnormality processing is finished the follow-up flow process of source program, directly withdraw from this scheduling or skip the follow-up one section code of source program after continue to carry out.
9. as the system of claim 7 or 8 described realization embedded software unconventionality testings, it is characterized in that,
Abnormality test point insert module, it is grand also to be used for inserting abnormality processing at source code, the grand data message that comprises message format of abnormality processing.
10. the system of realization embedded software unconventionality testing as claimed in claim 7, it is characterized in that, abnormality test script editor module, also be used for for the test script that has write, but the needs real time modifying scripted code during according to operation, do abnormality processing by new unusual formation condition, the different abnormal conditions of test same position.
CNB2007103023715A 2007-12-25 2007-12-25 A kind of method and system that realize embedded software unconventionality testing Expired - Fee Related CN100543701C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB2007103023715A CN100543701C (en) 2007-12-25 2007-12-25 A kind of method and system that realize embedded software unconventionality testing

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CNB2007103023715A CN100543701C (en) 2007-12-25 2007-12-25 A kind of method and system that realize embedded software unconventionality testing

Publications (2)

Publication Number Publication Date
CN101183335A CN101183335A (en) 2008-05-21
CN100543701C true CN100543701C (en) 2009-09-23

Family

ID=39448622

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB2007103023715A Expired - Fee Related CN100543701C (en) 2007-12-25 2007-12-25 A kind of method and system that realize embedded software unconventionality testing

Country Status (1)

Country Link
CN (1) CN100543701C (en)

Families Citing this family (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101582050B (en) * 2009-06-22 2012-02-08 阿里巴巴集团控股有限公司 Bug prompt method in software test and device
CN101833498B (en) * 2009-07-31 2012-06-06 北京伟晨豪嘉科技有限责任公司 Automatic detection system of embedded type system based on testing script technique
CN101697144A (en) * 2009-10-28 2010-04-21 中兴通讯股份有限公司 Software test method and software test device
CN103049370A (en) * 2011-10-17 2013-04-17 中兴通讯股份有限公司 Method and device for processing expected events intelligently in automated testing
CN103577317B (en) * 2012-08-02 2017-02-08 百度在线网络技术(北京)有限公司 Software system, exception testing method for same and software testing system
CN103019830B (en) * 2012-12-31 2016-09-21 深圳Tcl新技术有限公司 Realize the method and device of browser script language execution fault tolerance
CN104834590B (en) * 2014-02-11 2018-11-23 腾讯科技(深圳)有限公司 Method for testing software and system
CN107229558B (en) * 2016-03-23 2020-10-16 阿里巴巴集团控股有限公司 Software testing method and device
CN107291613B (en) * 2016-04-13 2020-06-05 阿里巴巴集团控股有限公司 Functional node abnormity simulation method and device
CN106326107B (en) * 2016-07-27 2019-03-08 北京计算机技术及应用研究所 Non-intrusion type embedded software abnormal based on simulated environment handles verification method
CN106874137A (en) * 2017-03-16 2017-06-20 深圳市茁壮网络股份有限公司 A kind of JS engine fault-tolerants method and apparatus
CN107678944B (en) * 2017-09-04 2020-12-29 中国航空工业集团公司西安飞行自动控制研究所 Automatic testing method based on embedded script
CN109240908B (en) * 2018-08-01 2020-04-03 口碑(上海)信息技术有限公司 Method and device for creating abnormal test case template
CN109324974A (en) * 2018-10-09 2019-02-12 郑州云海信息技术有限公司 It is a kind of to control the method and device for executing in batches script
CN109308265A (en) * 2018-10-26 2019-02-05 广州酷狗计算机科技有限公司 The method and apparatus for generating negative testing use-case
CN109783379B (en) * 2019-01-03 2022-02-08 北京云测信息技术有限公司 Script execution exception determining method and device
CN110457630B (en) * 2019-07-30 2022-03-29 北京航空航天大学 Method and system for identifying abnormal praise user in open source community
CN111008149B (en) * 2019-12-20 2023-08-22 广州品唯软件有限公司 Software testing method, software testing device and medium
CN114741274B (en) * 2021-01-08 2024-07-26 腾讯科技(深圳)有限公司 Abnormality testing method and device
CN113568796B (en) * 2021-08-04 2024-09-10 上海肇观电子科技有限公司 Module testing method and device

Also Published As

Publication number Publication date
CN101183335A (en) 2008-05-21

Similar Documents

Publication Publication Date Title
CN100543701C (en) A kind of method and system that realize embedded software unconventionality testing
CN113034095B (en) Man-machine interaction method and device combining RPA and AI, storage medium and electronic equipment
CN101777004B (en) Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment
Binkley et al. Automated refactoring of object oriented code into aspects
CN106775744B (en) Method and device for generating static library
CN104866298A (en) Flow chart based process business implementing method and device
US20090125874A1 (en) Method and system for creating projects in a rational application developer workspace
EP2697715A1 (en) System and method for mobile application development
CN111857801B (en) Construction method of mobile application
CN112148278A (en) Visual block chain intelligent contract framework and intelligent contract development and deployment method
CN110569050A (en) Applet updating method and device
CN109766139B (en) Configuration method and device of configuration file
CN111966357A (en) Operating system application compiling method and device and electronic equipment
CN112650487A (en) Hybrid application development method, system, computer device and storage medium
CN113986741A (en) Component debugging method and device and computer equipment
CN116629172A (en) Method, device, equipment and medium for automatically generating and integrating modules in chip design
KR102397494B1 (en) Low code web development and operating system, and service method using of it
CN103605526A (en) Template componentized code generating method based on chain-of-responsibility pattern
KR20030044959A (en) A Method for Implementing and Assembling Software Components using Client-Side Metadata and Glue Codes
KR100994070B1 (en) A Reserved Component Container Based Software Development Method and Apparatus
CN113032004B (en) Method, apparatus and program product for managing development jobs in a development environment
CN112631563A (en) System development method and device based on framework, computer equipment and storage medium
CN110908767B (en) Automatic parameter deployment method and device
CN110795067A (en) Demand prototype reusable method
CN116225415A (en) Front-end engineering method and system

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20090923

Termination date: 20141225

EXPY Termination of patent right or utility model