CN100527650C - Intelligent business testing method based on structural unit - Google Patents
Intelligent business testing method based on structural unit Download PDFInfo
- Publication number
- CN100527650C CN100527650C CNB031212980A CN03121298A CN100527650C CN 100527650 C CN100527650 C CN 100527650C CN B031212980 A CNB031212980 A CN B031212980A CN 03121298 A CN03121298 A CN 03121298A CN 100527650 C CN100527650 C CN 100527650C
- Authority
- CN
- China
- Prior art keywords
- parameter
- ase
- testing
- application service
- service element
- 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
Links
- 238000012360 testing method Methods 0.000 title claims description 47
- 238000010998 test method Methods 0.000 claims abstract description 11
- 238000000034 method Methods 0.000 claims description 13
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 230000006870 function Effects 0.000 abstract description 9
- 230000008569 process Effects 0.000 description 6
- 238000013461 design Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 4
- 230000008859 change Effects 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 241001672694 Citrus reticulata Species 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000052 comparative effect Effects 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000007689 inspection Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000003032 molecular docking Methods 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 238000004088 simulation Methods 0.000 description 1
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
An intelligent service test method based on structural members includes using automatic tester to program test example, presetting the input parameters of application service element (ASE) in the example, adding main service to the example, running the example to trigger to ASE by main service and transfer the input parameters to ASE, and verifying the output parameters transferred from ASE to main service for judging the relative functions of ASE is realized.
Description
Technical field
The present invention relates to the test of IN service, specifically, relate to IN service method of testing based on componentization.
Background technology
In the development process of TELLIN business, there is following problem:
The card number service version is many, and is individual surplus present wired card number service version has 50;
Professional SIB number is at 2000-3000, and quantity is many, and is difficult in maintenance;
Allocation list is many, and efficient is poor, and is maintainable poor; For example the UCS traffic table is 55;
Professional serial exploitation, the construction cycle is long;
The identity function module can not be shared;
Because the operation flow change is frequent, test case can not be reused;
Data list structure difference is big, and one card for multiple uses, unified voucher center class demand are not had solution preferably;
In order to solve or to alleviate the problems referred to above, proposed the notion of iCard solutions card number service solution, basic thought is that public traffic performance is extract, as the basic service member, be called Application Service Element (Application Service Entity is called for short ASE).The iCard solution mainly is based on the platform capabilities that the IIN-B02 version can provide, to the exploration of the new pattern in aspects such as card number service (perhaps IN service) exploitation, test, issue.
The iCard solution as shown in Figure 1.
ICard mainly explores card number development and maintenance pattern aspect several following:
1, the parallel distributed of card number service exploitation;
2, set up unified card number class Service Database rule;
3, hierarchical design, the business datum aspect is separated with the service logic aspect;
4, traffic performance shares etc.
The shortcoming of prior art is: 1) test at business function, it is correct to pay attention to operation flow, and docking port is paid close attention to less, is not suitable for testing ASE.2) to relate to content more for test case, and because of the modification of function and interface will cause the variation of use-case, discomfort is fit to do automation.
Summary of the invention
The object of the present invention is to provide a kind of IN service method of testing based on componentization, interface is correct during with the assurance test.
Method of testing of the present invention comprises step:
A, employing automatic testing instrument are worked out test case, preset the input parameter of Application Service Element (ASE) in test case;
B, work out corresponding trunk business, and this trunk business is joined in the test case according to tested Application Service Element;
C, operation test case make the professional triggering of trunk Application Service Element (ASE), and input parameter is passed to Application Service Element (ASE);
Whether D, test case to the output parameter that application business unit (ASE) passes to the trunk business are verified realize with the corresponding function of judging this Application Service Element (ASE).
According to said method:
Described testing tool is AutoService or SoftPhone.
Described test case comprise preliminary treatment script (PRESH) partly, call out collection part and judgment part, input parameter is partly realized at PRESH.
Presetting input parameter realizes by set up an interim parameter list for each Application Service Element (ASE).
Described parameter list comprises a plurality of input parameter items and a plurality of output parameter item.
Described parameter list passes through manual creation.
In the input parameter item, preset corresponding value during the preset parameter table, the output parameter item is put sky.
The PRESH of use-case partly makes each use-case with the deletion earlier of the record in the ASE parameter list, inserts a new record again, can correctly read parameter in the table to guarantee the trunk business.
Beneficial effect of the present invention: use simulation trunk business-driven business component, can effectively get rid of the influence of other parts in the trunk, make test can be absorbed in business component; Based on the parametric configuration use-case of member, help ensureing the completeness of use-case; Help test exemple automation.
Description of drawings
Fig. 1 is an iCard solution schematic diagram;
Fig. 2 is the model structure chart of ASE;
Fig. 3 is a flow chart of the present invention;
Fig. 4 selects the ASE structural representation for category of language.
Embodiment
ASE is with respect to former business, and on scale, meeting is little a lot, and the strategy of taking to divide and rule to test provides possibility.The abstract ASE that sees, its pattern as shown in Figure 2.
Have four kinds of input sources can influence the execution of ASE internal process, and the implementation of ASE and result also can monitor by corresponding four kinds of outputs.
Implementation method of the present invention is consulted Fig. 3: at first, adopt automatic testing instrument establishment test case, and preset the input parameter of Application Service Element (ASE) in test case; Secondly, work out corresponding trunk business according to tested Application Service Element, and this trunk business is joined in the test case; Afterwards, the operation test case makes the professional triggering of trunk Application Service Element (ASE), and input parameter is passed to Application Service Element (ASE); At last, whether test case to the output parameter that application business unit (ASE) passes to the trunk business is verified realize with the corresponding function of judging this Application Service Element (ASE).
The design of use-case
1, the combination of input parameter value condition
From the characteristics of ASE as can be seen, along with the function difference of ASE, the difference of the input and output object that relates under worse situation, influences the input meeting more complicated of ASE implementation, and manual test may be difficult to reach gratifying coverage rate.As: certain ASE has 3 input parameters, need read the field one by one in the privately owned table, needs the user to import two data, need send message one time to external module, 5 fields are arranged in the message, integrate, mean that this ASE has 3+1+2+5=11 input parameter.Suppose four kinds of value condition of each parameter consideration " maximum, minimum, intermediate value, unusual ", complete combination also has the combination of 4^11=4194304 kind.According to present case, even if the test of employing instrument will cover all input conditions fully, also be unlikely, need manual analysis, merge certain situation.But fortunately, this number is compared with the input complexity of an independent business in the past, reduced a lot, is not need the number that adopts scientific notation to represent at least.
Under the actual conditions, it is also conceivable that, if two parameters without any association, these two parameters also needn't make up.
In any case this numerical value probably still will break away from the manual scope that can carry out, the way of solution is to strengthen research on the one hand, finds out effective combined method, reduces the use-case number, is to carry out automatic test on the other hand.
2, judge covering
Constitute piece (being called for short SIB) based on the comparison in the flow process and branch's independent of service, design a collection of use-case, make each relatively three kinds of comparative results of SIB (greater than, equal, less than) occur once at least, every branch of each SIB of branch all is performed once.
Reach and judge covering, can't guarantee to reach SIB covering and branch and cover, but can verify that at least each is judged and the SIB of branch can select correct branch's flow process.
3, SIB covers
Reaching on the basis of judging covering, suitable combination comparison and the condition of the SIB of branch increase a collection of use-case, can guarantee to reach SIB and cover.
After platform provides SIB coverage rate statistical tool, can observe of the contribution of specific use-case according to statistics for the SIB coverage rate.After carrying out a collection of use-case, can also observe out according to statistics and be performed the higher SIB of frequency ratio, help to find the bottleneck point on the performance.
4, branch covers
Because business is a kind of network structure, it is bigger to reach branch's covering difficulty.
At present can only be rule of thumb and the characteristic of concrete ASE, draft the use-case that covers the main branch of ASE.
Automatic test
The automatic test of ASE will improve the development efficiency of automatic test case on the one hand, to catch up with the version pace of change of ASE, when use-case designs, also will consider stability on the other hand, the overlapping development of automatic test case when as far as possible reducing the ASE version updating more.
Instrument can be selected AutoService or SoftPhone for use.
At first, each ASE is relatively independent, each ASE calls by the trunk business, therefore by writing a simple trunk business, after guaranteeing to accomplish to move the trunk business, can trigger the ASE that will survey, promptly pass to the required input parameter of ASE by trunk, test the internal operation of ASE, the output parameter of passing to trunk by ASE verifies whether each function of this ASE realizes then.
Preset different input parameters and can consider to set up an interim ASE parameter list separately at each ASE, the form of table is as follows:
Input parameter 1 | Input parameter 2 | ... | Input parameter n | Output parameter 1 | Output parameter 2 | ... | Output parameter n |
The establishment of this table has two kinds of methods: a kind of is professional the generation, and a kind of is manual creation.Consider that professional to generate the mode of creating maintainable poor, change to need behind the list structure business recompilated and generate, therefore advocate to write SQL statement and build table by hand, not only intuitively but also be convenient to maintenance.
All input parameters, output parameter can find in each ASE Software Requirements Specification (also called requirements analysis).
Can adopt automatic testing instrument AutoService to write test case then.Mention above, have the operation that 4 kinds of input sources have influence on ASE, wherein the input parameter of trunk, can partly realize at PRESH, promptly insert a specific record to the ASE of interim establishment parameter list, it is just passable to note only needing to give each input parameter field preset value, and output parameter is empty; Privately owned table that need be by ASE among the DB, the parameter that total table reads in also can partly realize at PRESH, as long as just passable toward these table preset values; For the parameter of manually importing at the ASE internal user, can in the PCR operation of calling out collection, write realization; For the situation of roaming, can utilize the automatic return messages of automatic recovery message function of FEPTEST instrument to give business, therefore, can write the automatic use-case of AutoService equally and test as long as guarantee that environment is correct.
PRESH should be noted that partly each use-case all should insert a new record again with the deletion earlier of the record in the ASE parameter list, and the assurance business can correctly read.In the judgment part,,, should judge also whether each output parameter in the ASE parameter list conforms to expection as ticket, log sheet, remaining sum, base matrix section field etc. except the judgement of routine.
Give one example below and illustrate.
Select ASE such as category of language, structure as shown in Figure 3:
Input parameter when wherein, trunk calls is:
Parameter name | Type | Span | Meaning |
ServiceKey | IntegerType | Service key |
The output parameter that returns trunk is:
Parameter name | Type | Span | Meaning |
RetumCode | Char(2) | 00: success 01: the failure outlet | Return code is if be 01 then the direct call release of trunk flow process; |
LanguageType | Char(1) | 1~3 | Prompt tone kind: 1, mandarin; 2, English; 3, dialect |
Then we can create as following table (table name can be distinguished with the numbering of this ASE specification, for example ASE_T0102):
Field | Type | Span | Meaning |
ServiceKey | IntegerType | Service key | |
ReturnCode | Char(2) | 00: success 01: the failure outlet | Return code is if be 01 then the direct call release of trunk flow process; |
LanguageType | Char(1) | 1~3 | Prompt tone kind: 1, mandarin; 2, English; 3, dialect |
Write a trunk business (supposing service key 208) then, read in the input parameter (being exactly the value of ServiceKey) in the ASE_T0102 table here, call category of language and select ASE; After the ASE internal operation is finished, carry output parameter and return trunk, trunk carries out subsequent treatment, and output parameter is put into the ReturnCode and the LanguageType of ASE_T0102 table.The input parameter here is in the PRESH of Autoservice use-case part assignment.Specifically can be with reference to following:
The PRESH part:
dbaccess $TELLIN_DBNAME<<!
Delete from ASE_T0102;
Insert into ASE_T0102 values(′208′,null,nu11);
... (presetting the value of each allocation list of ASE)
!
Call out the collection part:
SSP tc_begin tc_invorkIDP trunk portion
SCP tc_continueltc_invorkRRBE
……
SCP tc_continue2tc_invorkP AASE part
SSP tc_continue2tc_invorkSRR
SCP tc_continueltc_invorkPC
SSP tc_continue2tc_invorkPCR
……
The ERB trunk portion
RC
The judgment part:
DB:
Row 1
Dbname $TELLIN_DBNAME
TableASE_T0102
WhereReturnCode=′00′and LanguageType=′1′
... (other judgement)
The configuration of each input parameter when initial conditions will call according to trunk, the privately owned table that ASE will use and publicly-owned table, the user of ASE inside input etc. are made up, if complete combination, may be very huge, therefore need remove the condition combination that can not occur according to actual conditions, perhaps, design reasonable, effective automatic test case without any the condition combination of association.
Method of the present invention, the input and output result's of interface parameters inspection problem when having solved ASE isolated operation test, and provide convenience to test exemple automation.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claims.
Claims (8)
1, a kind of IN service method of testing based on componentization is characterized in that comprising step:
A, employing automatic testing instrument are worked out test case, preset the input parameter of Application Service Element in test case;
B, work out corresponding trunk business, and this trunk business is joined in the test case according to tested Application Service Element;
C, operation test case make the professional triggering of trunk Application Service Element, and input parameter is passed to Application Service Element;
Whether D, test case to the output parameter that the application business unit passes to the trunk business are verified realize with the corresponding function of judging this Application Service Element.
2, method of testing as claimed in claim 1 is characterized in that: described testing tool is AutoService or SoftPhone.
3, method of testing as claimed in claim 1 is characterized in that: described test case comprise preliminary treatment script (PRESH) partly, call out collection part and judgment part, input parameter is partly realized at PRESH.
4, as claim 1,2 or 3 described methods, it is characterized in that: preset input parameter and realize by set up an interim parameter list for each Application Service Element.
5, method of testing as claimed in claim 4 is characterized in that: described parameter list comprises a plurality of input parameter items and a plurality of output parameter item.
6, method of testing as claimed in claim 4 is characterized in that: described parameter list passes through manual creation.
7, method of testing as claimed in claim 5 is characterized in that: preset corresponding value during the preset parameter table in the input parameter item, the output parameter item is put sky.
8, method as claimed in claim 3 is characterized in that: preliminary treatment the Script section of use-case makes each use-case with the deletion earlier of the record in the Application Service Element parameter list, inserts a new record again, can correctly read parameter in the table to guarantee the trunk business.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB031212980A CN100527650C (en) | 2003-03-31 | 2003-03-31 | Intelligent business testing method based on structural unit |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB031212980A CN100527650C (en) | 2003-03-31 | 2003-03-31 | Intelligent business testing method based on structural unit |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1534905A CN1534905A (en) | 2004-10-06 |
CN100527650C true CN100527650C (en) | 2009-08-12 |
Family
ID=34285655
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB031212980A Expired - Fee Related CN100527650C (en) | 2003-03-31 | 2003-03-31 | Intelligent business testing method based on structural unit |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN100527650C (en) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100407663C (en) * | 2004-11-17 | 2008-07-30 | 中兴通讯股份有限公司 | General test system and method for telecommunication intelligent service |
CN100377108C (en) * | 2005-04-30 | 2008-03-26 | 华为技术有限公司 | Executing method for test samples |
CN100363906C (en) * | 2006-02-28 | 2008-01-23 | 华为技术有限公司 | Method for testing software unit |
CN101221530B (en) * | 2008-01-22 | 2010-06-16 | 中兴通讯股份有限公司 | Method for automatically leading in test cases |
CN107329895B (en) * | 2017-06-21 | 2020-08-21 | 福建中金在线信息科技有限公司 | Test method and device for modular test case |
CN116186079B (en) * | 2023-04-27 | 2023-07-04 | 江苏博云科技股份有限公司 | Automatic rewriting and optimizing method for SQL batch queries |
-
2003
- 2003-03-31 CN CNB031212980A patent/CN100527650C/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
数据传输线路差错检测方法和分析. 马光星.中国数据通信,第12期. 2002 * |
Also Published As
Publication number | Publication date |
---|---|
CN1534905A (en) | 2004-10-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN107193545B (en) | Component-oriented multi-language collaborative development device, method and system | |
CN101377759B (en) | Automatic interface test system | |
CA2392675C (en) | Database system and method | |
US6014670A (en) | Apparatus and method for performing data transformations in data warehousing | |
CN110597842B (en) | Service data query method and system | |
CN105913233A (en) | SDK processing method suitable for application client end payment | |
CN101272281A (en) | A system and method for providing network services involving four parties | |
CN102096845A (en) | Knowledge base full text search engine system for classified forest management | |
CN102609451A (en) | SQL (structured query language) query plan generation method oriented to streaming data processing | |
CN106372044A (en) | Method for generating typed dimension XBRL (Extensible Business Reporting Language) report based on report form | |
CN112347071A (en) | Power distribution network cloud platform data fusion method and power distribution network cloud platform | |
CN109684609A (en) | A kind of Excel template generation and data conversion and introduction method based on ASP.NET MVC | |
CN110069248A (en) | Call method, device, equipment and the computer readable storage medium of interface data | |
CN100527650C (en) | Intelligent business testing method based on structural unit | |
CN107423223A (en) | Test and management system | |
CN109582286A (en) | Data standard method of calibration and its device based on Freemarker technology | |
CN102123099B (en) | Message processing system and method | |
CN202143092U (en) | Message processing system | |
CN110334001A (en) | A kind of method and apparatus that batch automatically generates echo test | |
CN108647018A (en) | Can live preview code generating system | |
Dalal et al. | AETG/sup SM/Web: a Web based service for automatic efficient test generation from functional requirements | |
CN102811445B (en) | Method and device for checking configuration data | |
CN105404608A (en) | Formula analysis based complicated index set calculation method and system | |
CN110147406A (en) | A kind of visual numeric simulation system and its framework method towards cloud computing | |
CN115237392B (en) | Database code generation and updating method and system in data circulation 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 | ||
C17 | Cessation of patent right | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20090812 Termination date: 20130331 |