CN1641601A - Software unit measuring method - Google Patents
Software unit measuring method Download PDFInfo
- Publication number
- CN1641601A CN1641601A CN 200410002352 CN200410002352A CN1641601A CN 1641601 A CN1641601 A CN 1641601A CN 200410002352 CN200410002352 CN 200410002352 CN 200410002352 A CN200410002352 A CN 200410002352A CN 1641601 A CN1641601 A CN 1641601A
- Authority
- CN
- China
- Prior art keywords
- function
- tested
- stake
- test
- 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
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a software unit testing method. The software can be separated into several units that each of them has corresponding function. The method can be realized according to the following steps: starting testing program; setting the stake circumstance and database circumstance that can supply the needed data of the tested unit; building up the input parameter of the tested unit needed and driving the tested unit to execute tested function or method; capturing the low layer data or external data that the tested function or method needed form stake circumstance or database circumstance; checking the output of the tested function or method to know whether the tested unit is normal.
Description
Technical field
The present invention relates to the measuring technology of software, relate in particular to a kind of unit test method of software.
Background technology
Unit testing be to each module of software carry out the most targeted, cover the most comprehensive, systematicness test the most completely.Unit testing is for the leak (bug) in the early stage abundant discovery procedure of exploitation, and the stable and stalwartness of raising program is extremely important.But, increase day by day along with software size, how each module of software is carried out fully effectively unit testing, the unit testing use-case that how design management quantity is huge, how allowing unit testing become an activity robotization, that can repeat all becomes distinct issues.
Fig. 1 is an inner structure (other software systems can adopt similar chromatographic analysis method) based on the large-scale distributed software systems backstage of database, and this system backstage adopts C++ to write, from being divided into three levels in logic:
Business treatment (TASK) is handled concrete service logic;
Public functional layers (Public Function), the function interface of abstract part public function;
Database interface layer (DBI Function), accessing database.
As can be seen from the figure, this software systems hierarchical relationship is simple relatively, but the call relation more complicated between each layer.And, the function that each layer provides has than big-difference, module operation context environmental also has nothing in common with each other: the TASK business module is based on that message event mechanism triggers, public function module in the middle of being positioned at call and the interface that is called all is a local code, and relational database (DBI) interface layer downwards directly and database mutual.
For the huge software configuration of this comprehensive complexity, mainly contain following two kinds of method of testings in the prior art:
Method one, in code direct structure false data,, be in " normal operation " mode or " unit testing " mode by running status grand or the configuration file control program.Automatically move if the latter then drives tested code, directly return the false data of structure at the interactive interface place.
The advantage of this implementation is to treat source code and unit testing code with a kind of uniform way.But, still have following deficiency because implementation is more coarse:
1, can't fully cover all source codes.Particularly directly return false data thereby interface codec functions that can't test interface module itself in interface module;
2, the data configuration amount is big and loaded down with trivial details, and a large amount of test environment data are difficult to reuse and manage;
3, in source code, need to insert the grand or condition judgment of a large amount of conditions, easily source code is damaged.
Method two,
Using specific program to send to the software backstage by forwards center (MDP) and send message, whether to Message Processing correct, as shown in Figure 2 if observing the backstage.
This mode is actually based on interface testing (being integration testing) rather than based on the unit testing of code itself.Therefore, this mode exists following many shortcomings:
1, driving use-case itself is directly not corresponding with tested code, and the writing of test case code is separated loaded down with trivial details and inefficiency with the source code writing;
2, use-case drives and the result judges and needs manual intervention, and it is high and be difficult to reuse to carry out efficient;
3, the illegal branch that is difficult to test procedure.
Summary of the invention
The object of the present invention is to provide a kind of unit test method of software, exist efficient low and test inadequate problem in the existing test to solve.
Realize technical scheme of the present invention:
A kind of unit test method of software, described software is from being divided into the unit of a plurality of realization corresponding functions in logic, and the method comprising the steps of:
Start test case;
Setting can provide the anchor ear border or the database environment of unit under test desired data;
Structure unit under test required input parameter, and drive unit under test and carry out tested function or method, following layer data or external data that this tested function or method need are obtained from anchor ear border or database environment;
Whether the output of checking tested function or method is working properly with the checking unit under test.
According to said method:
By the identical pile function of the tested function/class function/stake class in definition and the unit under test in test case the anchor ear border is set, and in unit under test, inserts stake and realize that call back function obtains a data from the anchor ear border.
Adopt the macro substitution mode to insert stake in unit under test, promptly in the head predefine pile function and/or the stake class of software, the function/class with unit under test when test replaces with pile function/stake class.
Adopt the NameSpace switching mode to insert stake in unit under test, i.e. the name of pile function is named identical with the lower floor's interface function that is replaced but is in different NameSpaces, and at the head of software the NameSpace that needs switch to is defined.
By distinguish the public property of pile function for zone bit of each interface assignment, when calling pile function, this zone bit is decomposed, and return corresponding stake data according to different situations.
By calling the database common interface function setup database environment in the tested software, or by the direct visit data lab setting database environment of Structured Query Language (SQL) (SQL), or database environment is set, or database environment is set by the data importing mode by carrying out database script.
Described database environment is a real database environment in the tested software.
If function output rreturn value is then directly judged function return value; If tested function is by calling other interface return messages, then in tested class, increase a member variable, before returning, function, checks during the checking function that this member variable record is to judge the rreturn value of tested function to this member variable assignment.
The present invention has following beneficial effect:
1, needn't destroy source code, the insertion source code that the unit testing code can be seamless, and adopt identical configuration management mode with source code.
2, increase work efficiency, the test of convenient unusual branch, self-test (BVT) operation automatically after the compiling, mistake error correction and code development carry out synchronously.
3, the operation of artificial intervention can robotization not be had in unit testing; Can cover automatically after code revision and check all correlative codes, location of mistake is more convenient and easy.
Description of drawings
Fig. 1 is the inner basic structure synoptic diagram in certain distributed software system backstage;
Fig. 2 is by carrying out the unit testing synoptic diagram in the forwards center;
Fig. 3 is a method of testing process flow diagram of the present invention
Fig. 4 carries out unit testing for the present invention to this software systems backstage framed structure synoptic diagram.
Embodiment
Consult shown in Figure 3ly, testing process of the present invention is as follows:
Step 10: start unit test case;
Step 20: setting can provide the anchor ear border or the database environment of unit under test desired data;
Step 30: the required input parameter of structure unit under test;
Step 40: drive unit under test and carry out tested function or method, following layer data or external data that this tested function or method need are obtained from anchor ear border or database environment;
Step 50: whether the output of checking tested function or method is working properly with the checking unit under test.
If function output rreturn value is so directly judged function return value to get final product; If tested function by calling other interface return messages, can increase a member variable so in tested class, to this member variable assignment, the checking function checked that this member variable writes down the rreturn value that can judge tested function before function returned.
Method is a concrete behavior, and the result that method is carried out will change or export specific data.Whether correct by checking that these reformed data come determination methods to carry out.
After the start unit test case, finish automatically by test case step 20～50.Be that example is elaborated software backstage shown in Figure 1 is carried out unit testing below:
Consult shown in Figure 4ly, the function that realizes according to each layer module in the software is different with the context environmental of operation dependence, need take different Test Strategies for different levels; The solidified cell test case is taked the way to manage consistent with source code to unit testing code and use-case; And adopt the method for self-test (BVT, Buildverification Tests), guarantee that the driving of unit testing and checking can automatically perform and judge.
The solidified cell test case is meant that the unit testing use-case uses the mode of hard coded to write in the middle of the test code, and the status of test code and tested code is an equality, all be placed in the repository and manage, test code is not the accessory that adds of tested code, so cry " curing "." automatically perform judgement " exactly because the result of solidifying.Therefore being placed in the repository of test code and tested code equality not only comprised the business function that tested code is realized in the executable file beta version that compiling is come out, and also just comprised simultaneously the test function of test code.According to the framework that test code provides, can generate necessary environmental data, the tested code of autonomous driving is carried out, and judges the result who carries out; All these do not need manual intervention, only need to start executable test procedure and get final product.
1, the unit testing of operation layer code
The operation layer on this distributed software system backstage is based on message event mechanism.In order to make the operation of its " independently ", must construct corresponding input message and call the service message call back function.Comprise with the code dependent unit testing code of operation layer:
Initialization section: correct anchor ear border or database environment are set.
Drive part: the structure input parameter drives the execution (substituting operating message dispatch function) of message call back function.
Verification portion: check the output of tested function/class.
For the test of service code, crucial building in the stake data.The stake data have substituted really layer data down, and its indirect brings great convenience for test and be flexible.But be to use stake must under the situation of not destroying source code, insert stake; Simultaneously, because during the identical public function of a plurality of module invokes, identical public function is inevitable also to be replaced by same stake, thereby must guarantee that these identical stakes can be public by different module institutes.
For the insertion of stake, can switch by macro substitution or NameSpace and realize that what adopt in the unit testing framework of present embodiment is the method for macro substitution.If for overall situation function piling, so directly function is replaced with pile function, corresponding pile function is identical with the interface that is replaced function; If be class piling, so directly class name is replaced with the title of a class, the public method that the stake class provides is identical with the public method of the class that is replaced.As:
Specific grand _ TOPO_UT_ in, macro substitution is GetSubnetByUser_utStub to overall situation function GetSubnetByUser; So, (promptly in compilation script file makefile, define _ TOPO_UT_ is grand) under the unit testing situation, that in fact call in the place of the function G etSubnetByUser that all call is unit testing pile function GetSubnetByUser_utStub, provides specific test data by this function; And under normal operation, _ TOPO_UT_ is grand not to be defined, routine call be exactly GetSubnetByUser function itself, obtain descending really layer data.Under the mode that NameSpace switches, the lower floor's interface function that is replaced is identical with the pile function name, but is in the different NameSpaces.Switch to corresponding NameSpace and get final product according to grand whether definition of unit testing at the top of file of tested software, its essence is identical with the macro substitution method.
Be the example of a typical service code unit testing drive part below:
Void CGetCustomer_utDrive ∷ testGetCustomerInfoReqCB () // call member function to build specific environment, pile function environment setupEnv () is set; G_utFlag_CheckTrailRight=UTFLAG_RETURN_TRUE; // structure request msg, i.e. the input message GetCustomerInfoREQ req of tested function; Req.resize (1); Req[0]=1; MDP ∷ Message msg (TOP_GET_CUSTOMERINF_REQ, req); // invocation target code is to show the message call back function CGetCustomer target that calls Business treatment here; Target.GetCustomerInfoReqCB (msg); // check the output of tested function, assert the correctness const GetCustomerInfoRSP ﹠amp that guarantees the result by what CPPUNIT provided; Amp; Rsp=target.m_rsp; CPPUNIT_ASSERT (3==rsp.customerInfoList.size ());
For the public property of stake, by being zone bit realization of each interface assignment.Zone bit has two classes: public sign position and individual zone bit.Public sign is used for defining public stake data, and individual zone bit defines own specific stake data by the individual.Simultaneously, public sign and individual's sign all comprise certain scope, are used for defining the stake data of various different situations.Synthetic and the decomposition of stake zone bit can realize by simple macro definition or inline function.In pile function, need resolve corresponding marker bit, return corresponding test data according to various situation.
Be that a code inserts a simple example below:
Grand #include " topoutcommon.h " the #define GetSubnetByUser GetSubnetByUser_utStub #define CSecurityAgentTask CSecurityAgentTask_utStub #endif of #include " resstring.h " #ifdef _ TOPO_ UT_ // be used for separating element test code // _ all codes of TOPO_UT_ // following in, every public function GetSubnetByUser part of calling all changes and transfers pile function GetSubnetByUser_utStub; Every class CSecurityAgentTask example part of using all is replaced by example as stake class CSecurityAgentTask_utStub
2, the unit testing of database interface code
The database interface layer on this software systems backstage directly is based upon on the Basis of Database.Generally speaking, there is not the complicated service logic in the database interface layer, is generally: data table name, field name mistake, database API Calls mistake etc.In order to test effect, the database interface layer identification code needn't be done stake in lower floor, but directly constructs real database environment, and whether test this layer identification code read and write access database function correct.Therefore, the driving of database interface test code and checking are all fairly simple, and key is how to build database environment.Can adopt following three kinds of methods according to different situations:
A, call ready-made database common interface function.This mode is changeable according to the actual conditions workload, and advantage is a code of having tested other parts in the lump; Shortcoming is to rely on by the correctness of mode transfer piece.Generally, if adopt bottom-up unit testing strategy to make in this way.
B, by the direct accessing database of Structured Query Language (SQL) (SQL).This mode is easier to data lab environment Data Control ratio, change also simple relatively, but workload is bigger, more loaded down with trivial details.Adopt this mode for simple database environment suggestion.
C, execution database script or data importing.This mode is most effective, operates also more convenient.But it must be complete requiring environment configurations.Generally, can consider a plurality of similar unit testing use-cases are concentrated in the comprehensive database environment, adopt the method for disposable importing just efficient and convenient relatively.
For different units, except adopting above-mentioned corresponding Test Strategy, the framework of method of testing of the present invention is preferably followed following common principle:
A, the code that all are relevant with unit testing use the grand packing of unit testing.Grand just can to control the program that variation comes out be unit testing version or release version by closing in Makefile or opening like this.
The key of B, test frame is exactly: " curing ", " robotization ", require unit testing code and source code unified management, source code must depend on the inspection and the checking of unit testing code, and requires all unit testing codes must be able to not have the automatic operation of artificial intervention.
C, use single programs inconvenience test part for other, such as with the interactive interface of other programs, all adopts the mode of stake replacement to test easily in the present invention.
From the above, the present invention has following characteristics:
Can hold the unit testing of multiple type of drive, can to complex large-sized software systems provide fully and Thoroughly unit testing;
Unit testing can be managed in an identical manner with source code, the weight of supporter test With;
Curable test case, simplify test logic, can the driver element test case automatically perform and right Execution result carries out automatic decision, need not manual intervention, thereby can guarantee the reusability of unit testing.
Though more than describe as an example of the distributed software system of a based on database example, of the present invention Be limited to this, all C++ programs all are sub-module, classification, branch function, and access this locality or network are arranged The calling interface of file or data system can adopt method of testing of the present invention.
Claims (11)
1, a kind of unit test method of software, described software is characterized in that from being divided into the unit of a plurality of realization corresponding functions in logic the method comprising the steps of:
Start test case;
Setting can provide the anchor ear border or the database environment of unit under test desired data;
Structure unit under test required input parameter, and drive unit under test and carry out tested function or method, following layer data or external data that this tested function or method need are obtained from anchor ear border or database environment;
Whether the output of checking tested function or method is working properly with the checking unit under test
2, the method for claim 1, it is characterized in that, by the identical pile function of the tested function/class function/stake class in definition and the unit under test in test case the anchor ear border is set, and in unit under test, inserts stake and realize that call back function obtains a data from the anchor ear border.
3, method as claimed in claim 2 is characterized in that, adopts the macro substitution mode to insert stake in unit under test, and promptly in the head predefine pile function and/or the stake class of software, the function/class with unit under test when test replaces with pile function/stake class.
4, method as claimed in claim 2, it is characterized in that, adopt the NameSpace switching mode in unit under test, to insert stake, be that the name of pile function is identical with the lower floor interface function name that is replaced but be in different NameSpaces, and the NameSpace that needs switch to defined at the head of software.
5, as claim 2 or 3 described methods, it is characterized in that,, when calling pile function, this zone bit is decomposed, and return corresponding stake data according to different situations by distinguish the public property of pile function for zone bit of each interface assignment.
6, the method for claim 1, it is characterized in that, by calling the database common interface function setup database environment in the tested software, or by the direct visit data lab setting database environment of Structured Query Language (SQL) (SQL), or database environment is set, or database environment is set by the data importing mode by carrying out database script.
As claim 1 or 6 described methods, it is characterized in that 7, described database environment is a real database environment in the tested software.
8, the method for claim 1 is characterized in that, the mode that unit under test and other unit or outside interactive interface adopt stake to replace realizes.
9, the method for claim 1 is characterized in that, if function output rreturn value is then directly judged function return value; If tested function is by calling other interface return messages, then in tested class, increase a member variable, before returning, function, checks during the checking function that this member variable record is to judge the rreturn value of tested function to this member variable assignment.
10, the method for claim 1 is characterized in that, all testing procedures all automatically perform after the startup test case.
11, the method for claim 1 is characterized in that, the code of test case with in repository, adopted identical management by methods by the code of software.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410002352 CN1641601A (en) | 2004-01-04 | 2004-01-04 | Software unit measuring method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 200410002352 CN1641601A (en) | 2004-01-04 | 2004-01-04 | Software unit measuring method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1641601A true CN1641601A (en) | 2005-07-20 |
Family
ID=34867363
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 200410002352 Pending CN1641601A (en) | 2004-01-04 | 2004-01-04 | Software unit measuring method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1641601A (en) |
Cited By (23)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100359488C (en) * | 2005-08-19 | 2008-01-02 | 华为技术有限公司 | Method for automatic generating random excitation based on percentage of function coverage |
| CN100363906C (en) * | 2006-02-28 | 2008-01-23 | 华为技术有限公司 | Method for testing software unit |
| CN100426253C (en) * | 2005-08-01 | 2008-10-15 | 中兴通讯股份有限公司 | Test method of a database depended software unit |
| CN100428252C (en) * | 2006-09-14 | 2008-10-22 | 华为技术有限公司 | System and method for testing and measuring percentage of coverage of function |
| CN100451988C (en) * | 2006-11-14 | 2009-01-14 | 无敌科技(西安)有限公司 | Method and system for realizing unit test |
| CN101261600B (en) * | 2007-03-06 | 2010-04-07 | 中兴通讯股份有限公司 | Software test apparatus and test software design method |
| CN101847117A (en) * | 2009-03-23 | 2010-09-29 | 中兴通讯股份有限公司 | Unit testing method and device |
| CN1952818B (en) * | 2005-10-22 | 2010-12-15 | 康佳集团股份有限公司 | Testing method of program unit with capability of checking test result automatically |
| CN102110049A (en) * | 2010-12-14 | 2011-06-29 | 中山大学 | Method and system for automatically testing digital television middleware interface |
| CN102360334A (en) * | 2011-10-17 | 2012-02-22 | 中国人民解放军信息工程大学 | Dynamic and static combined software security test method |
| CN101901184B (en) * | 2009-05-31 | 2012-09-19 | 西门子（中国）有限公司 | Method, device and system for inspecting vulnerability of application program |
| CN102819487A (en) * | 2011-06-10 | 2012-12-12 | 腾讯科技（深圳）有限公司 | Method and device for testing online game |
| CN102968371A (en) * | 2012-11-26 | 2013-03-13 | 武汉天喻信息产业股份有限公司 | Method and device for testing JAVA API unit component |
| CN103019931A (en) * | 2012-11-26 | 2013-04-03 | 华为技术有限公司 | Method and device for detecting and treating Asn.1 interfaces |
| CN103049378A (en) * | 2012-12-18 | 2013-04-17 | 惠州市亿能电子有限公司 | Program debugging method without emulator |
| CN105068937A (en) * | 2015-09-22 | 2015-11-18 | 浪潮(北京)电子信息产业有限公司 | Unit test method of Linux kernel module |
| CN105630679A (en) * | 2015-12-23 | 2016-06-01 | 北京奇虎科技有限公司 | Code testing method and apparatus |
| CN102289404B (en) * | 2010-06-15 | 2016-11-30 | 微软技术许可有限责任公司 | Based on performing to catch and the debugging of playback |
| CN107766244A (en) * | 2017-10-11 | 2018-03-06 | 中国计量大学 | A kind of intelligent electric energy meter software unit testing method |
| CN108845932A (en) * | 2018-05-24 | 2018-11-20 | 北京五八信息技术有限公司 | A kind of unit test method of network library, device, storage medium and terminal |
| CN109656806A (en) * | 2018-10-29 | 2019-04-19 | 口碑(上海)信息技术有限公司 | A kind of the playback test method and device of interface data |
| CN110597736A (en) * | 2019-10-31 | 2019-12-20 | 口碑(上海)信息技术有限公司 | Test data generation method and device |
| CN112559344A (en) * | 2020-12-10 | 2021-03-26 | 平安养老保险股份有限公司 | Remote mock testing method and system |
-
2004
- 2004-01-04 CN CN 200410002352 patent/CN1641601A/en active Pending
Cited By (29)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100426253C (en) * | 2005-08-01 | 2008-10-15 | 中兴通讯股份有限公司 | Test method of a database depended software unit |
| CN100359488C (en) * | 2005-08-19 | 2008-01-02 | 华为技术有限公司 | Method for automatic generating random excitation based on percentage of function coverage |
| CN1952818B (en) * | 2005-10-22 | 2010-12-15 | 康佳集团股份有限公司 | Testing method of program unit with capability of checking test result automatically |
| CN100363906C (en) * | 2006-02-28 | 2008-01-23 | 华为技术有限公司 | Method for testing software unit |
| CN100428252C (en) * | 2006-09-14 | 2008-10-22 | 华为技术有限公司 | System and method for testing and measuring percentage of coverage of function |
| CN100451988C (en) * | 2006-11-14 | 2009-01-14 | 无敌科技(西安)有限公司 | Method and system for realizing unit test |
| CN101261600B (en) * | 2007-03-06 | 2010-04-07 | 中兴通讯股份有限公司 | Software test apparatus and test software design method |
| CN101847117A (en) * | 2009-03-23 | 2010-09-29 | 中兴通讯股份有限公司 | Unit testing method and device |
| CN101847117B (en) * | 2009-03-23 | 2014-09-10 | 中兴通讯股份有限公司 | Unit testing method and device |
| CN101901184B (en) * | 2009-05-31 | 2012-09-19 | 西门子（中国）有限公司 | Method, device and system for inspecting vulnerability of application program |
| CN102289404B (en) * | 2010-06-15 | 2016-11-30 | 微软技术许可有限责任公司 | Based on performing to catch and the debugging of playback |
| CN102110049A (en) * | 2010-12-14 | 2011-06-29 | 中山大学 | Method and system for automatically testing digital television middleware interface |
| CN102819487A (en) * | 2011-06-10 | 2012-12-12 | 腾讯科技（深圳）有限公司 | Method and device for testing online game |
| CN102360334A (en) * | 2011-10-17 | 2012-02-22 | 中国人民解放军信息工程大学 | Dynamic and static combined software security test method |
| CN102360334B (en) * | 2011-10-17 | 2015-04-15 | 中国人民解放军信息工程大学 | Dynamic and static combined software security test method |
| CN103019931B (en) * | 2012-11-26 | 2015-12-02 | 华为技术有限公司 | The check processing method and apparatus of Asn.1 interface |
| CN102968371B (en) * | 2012-11-26 | 2015-09-23 | 武汉天喻信息产业股份有限公司 | The method of test JAVA API unit component and device |
| CN103019931A (en) * | 2012-11-26 | 2013-04-03 | 华为技术有限公司 | Method and device for detecting and treating Asn.1 interfaces |
| CN102968371A (en) * | 2012-11-26 | 2013-03-13 | 武汉天喻信息产业股份有限公司 | Method and device for testing JAVA API unit component |
| CN103049378A (en) * | 2012-12-18 | 2013-04-17 | 惠州市亿能电子有限公司 | Program debugging method without emulator |
| CN105068937A (en) * | 2015-09-22 | 2015-11-18 | 浪潮(北京)电子信息产业有限公司 | Unit test method of Linux kernel module |
| CN105068937B (en) * | 2015-09-22 | 2018-09-28 | 浪潮(北京)电子信息产业有限公司 | A kind of unit test method of Linux kernel module |
| CN105630679B (en) * | 2015-12-23 | 2019-04-23 | 北京奇虎科技有限公司 | The method and device of code tester |
| CN105630679A (en) * | 2015-12-23 | 2016-06-01 | 北京奇虎科技有限公司 | Code testing method and apparatus |
| CN107766244A (en) * | 2017-10-11 | 2018-03-06 | 中国计量大学 | A kind of intelligent electric energy meter software unit testing method |
| CN108845932A (en) * | 2018-05-24 | 2018-11-20 | 北京五八信息技术有限公司 | A kind of unit test method of network library, device, storage medium and terminal |
| CN109656806A (en) * | 2018-10-29 | 2019-04-19 | 口碑(上海)信息技术有限公司 | A kind of the playback test method and device of interface data |
| CN110597736A (en) * | 2019-10-31 | 2019-12-20 | 口碑(上海)信息技术有限公司 | Test data generation method and device |
| CN112559344A (en) * | 2020-12-10 | 2021-03-26 | 平安养老保险股份有限公司 | Remote mock testing method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1641601A (en) | Software unit measuring method | |
| CN1264106C (en) | Method for accessing database system uniformly | |
| CN1858704A (en) | Method of upgrading sequence | |
| CN101042645A (en) | Method, equipment and system for unionize software development environment | |
| CN1959640A (en) | System and method for representing user process to software package in software package management system | |
| CN1804840A (en) | Data access layer class generator | |
| CN1845120A (en) | Automatic analysis system and method for malicious code | |
| CN101067864A (en) | Long-distance controlling apparatus using for crops production expert diagnosing system and method thereof | |
| CN1710535A (en) | GIS application system and development method thereof | |
| CN1248116C (en) | General purpose testing arrangement for embedded module and subsystem based on host machine platform | |
| CN100351785C (en) | Method for debuging embedded system and equipment | |
| CN1673972A (en) | Dynamic monitoring system and method for data base list update | |
| CN101183310A (en) | Method for establishing apparatus drive, driving apparatus of equipment and board | |
| CN102221998A (en) | Method for extending EJB container in component running support platform | |
| CN1282085C (en) | Method of parallel regulating multi-task of imbedding system | |
| CN1841336A (en) | Computer testing method | |
| CN1967475A (en) | Development system of script command line | |
| CN1658159A (en) | Configurable and dynamically alterable object model | |
| CN1945527A (en) | SERVER edition code generation system capable of realizing code reutilizization | |
| CN1255744C (en) | Universal high speed IC card issuing apparatus and method | |
| CN100337216C (en) | Software test method | |
| CN1956445A (en) | Implementing method faced to gate package of web service | |
| CN1296820C (en) | Autonomous device driver | |
| CN1245685C (en) | Drive method based on structure operation system dynamic equipment | |
| CN1764131A (en) | Protocol testing system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |