CN103218295A - Method and system for testing message handling capacity of ESB (Enterprise Service Bus) - Google Patents
Method and system for testing message handling capacity of ESB (Enterprise Service Bus) Download PDFInfo
- Publication number
- CN103218295A CN103218295A CN2013101351068A CN201310135106A CN103218295A CN 103218295 A CN103218295 A CN 103218295A CN 2013101351068 A CN2013101351068 A CN 2013101351068A CN 201310135106 A CN201310135106 A CN 201310135106A CN 103218295 A CN103218295 A CN 103218295A
- Authority
- CN
- China
- Prior art keywords
- message
- esb
- service
- time
- request
- 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.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method and a system for testing the message handling capacity of an ESB (Enterprise Service Bus). The method comprises the following steps of simulating an ESB service flow; establishing an ESB service access script corresponding to the ESB service flow; simulating a message access queue, performing service request on the ESB according to the ESB service flow by use of the ESB service access script through each request message in the message access queue, and recording a time stamp on a key time node; and determining a test result according to the recorded time stamp corresponding to each request message. By utilizing the method, on the one hand, the data security of a service system is ensured, on the other hand, relevant information required for the test can be conveniently acquired; meanwhile, the message handling capacity of the ESB is determined according to the recorded time stamps, so that the test accuracy of the message handling capacity of the ESB is improved; and the method is convenient and rapid and can be used for improving the test efficiency.
Description
Technical field
The present invention relates to performance test field, the more particularly to a kind of method of testing and system of ESB message handling abilities.
Background technology
In order to realize the isolation of interior business service system and external business service request, the integration ensured information security with messenger service, many enterprises employ a kind of ESB (Enterprise Service Bus, ESB) this message set into software architecture.ESB can be used for eliminating the technological disparity between different application, allows different application service coordinate operations, realizes the communication and integration between different services, while can also isolate to the supplier of enterprises service and the requestor of service.Current ESB is widely used in different fields.Some enterprises are used as real time information inquiry and the interface of Real Data Exchangs even with ESB.Higher requirement thus is proposed to ESB message handling ability.
ESB message handling ability can be embodied by following parameter：The speed of response, user's connection speed and service processing speed.The speed of response refers to beginning to send out request to the speed for obtaining service response result completely from service requester in single request.Unit is generally every millisecond of request；User will ask service request to ESB, and a process established the link is had first.User's connection speed refers to a user by the speed successfully reached the standard grade after linked operation such as being authenticated, authorizing with ESB.It is per second that unit is generally user.Service processing speed refers to the speed that single service request has been processed in ESB, and service processing speed is different and different according to service processing complexity, and it is per second that unit is generally request.
Therefore a kind of method of testing is needed to obtain the ESB speed of response, user's link speed, the parameter such as service processing speed to reflect ESB message handling ability.The method of traditional measuring table disposal ability be in key on logging timestamp, by it is relatively more different when on timestamp obtain the period.But this method can not be applicable completely on ESB message processing times are obtained.Because the operations such as ESB user's link and service processing are completed in ESB softwares, it is impossible to record the timestamp of key node.
The content of the invention
It is an object of the invention to provide a kind of method of testing and system of ESB message handling abilities, it is capable of non-intrusive, efficient measurement ESB message handling ability.
The purpose of the present invention is achieved through the following technical solutions：
A kind of method of testing of ESB message handling abilities, comprises the following steps：
Simulate ESB operation flows；
Set up ESB service access script corresponding with the ESB operation flows；
Each request message simulated in message access queue, the message access queue carries out service request according to the ESB operation flows using the ESB service access script to ESB, and records the timestamp on material time node；
Test result is determined according to the corresponding timestamp of each solicited message of record.
A kind of test system of ESB message handling abilities, including：
Service analogue module, for simulating ESB operation flows；
Script generation module, for setting up ESB service access script corresponding with the ESB operation flows；
Message Simulation module, for simulating message access queue；
Performing module is asked, for when receiving test instruction, driving each request message in the message access queue to carry out service request to ESB according to the ESB operation flows using the ESB service access script, and the timestamp on material time node is recorded；
Data processing module, test result is determined for the corresponding timestamp of each solicited message according to record.
According to the scheme of the invention described above, it is in simulation ESB operation flows and after establishing ESB service access script corresponding with the ESB operation flows, each request message simulated in obtained message access queue carries out service request according to the ESB operation flows using the ESB service access script to ESB, and record the timestamp on material time node, test result is determined further according to the timestamp of record, due to simulating ESB operation flows, on the one hand it ensure that the data safety of operation system, another side is easy to obtain the relevant information required for testing again, simultaneously, ESB message handling ability is determined by the timestamp of record, improve the accuracy of ESB message handling ability test, it is simultaneously convenient, fast, improve testing efficiency.
Brief description of the drawings
Fig. 1 is the schematic flow sheet of the method for testing embodiment of the ESB message handling abilities of the present invention；
Fig. 2 be Fig. 1 in simulation ESB operation flows one embodiment refinement schematic flow sheet；
Fig. 3 be Fig. 1 in the one embodiment for setting up ESB service access scripts refinement schematic flow sheet；
Fig. 4 carries out the refinement schematic flow sheet of one embodiment of service request for each request message in the message access queue in Fig. 1 to ESB；
Fig. 5 is the refinement schematic flow sheet of one embodiment of location survey test result really in Fig. 1；
Fig. 6 is the structural representation of the test system embodiment of the ESB message handling abilities of the present invention；
Fig. 7 is the request process timing diagram of a message access queue for having two request messages.
Embodiment
With reference to embodiment and accompanying drawing, the present invention is further elaborated, but the implementation not limited to this of the present invention.
The schematic flow sheet of the method for testing embodiment of the ESB message handling abilities of the present invention is shown in Fig. 1.
As shown in figure 1, the method in the present embodiment includes step：
Step S101：Simulate ESB operation flows；
ESB is needed to access target service service when conformity of business operation, and ordinary business practice service is provided by different operation systems；It is unpractical to access real operation system using ESB in test process, on the one hand it cannot be guaranteed that data safety, another side can not obtain the relevant information required for test, so needing to be simulated business service；
Obtained ESB operation flows are simulated to be linked into ESB；
Step S102：Set up ESB service access script corresponding with the ESB operation flows；
ESB service because communication protocol, transmission means difference and access mode is also different, can be realized by configuration access script to some ESB service access；It is mainly the process of a generation ESB service access script in this step, while configuring related affairs, record script is by coefficient correlation when in use；
Step S103：Each request message simulated in message access queue, the message access queue carries out service request according to the ESB operation flows using the ESB service access script to ESB, and records the timestamp on material time node；
What message access queue described in this step was simulated is that user carries out service request to ESB, according to actual needs, can simulate the message access queue of varying number；The process that message access queue is once linked when ESB is entered；The user that can be obtained by the process in ESB Message Processings links speed, and ESB service processing speed can be obtained by message request；
Material time node can be selected according to actual conditions, and such as proceeding by the timing node of service request, each request message including each request message terminates the timing node of service request and the timing node of each request message arrival access target (such as ESB)；
Step S104：Test result is determined according to the corresponding timestamp of each solicited message of record；
This step can be determined for testing several parameters involved by ESB message handling ability by the corresponding timestamp of each solicited message of record：When response time, Connection Time, Message Processing, then determine by these parameters ESB message handling ability.
Accordingly, according to the scheme in above-mentioned the present embodiment, it is simulation ESB operation flows, and set up ESB service access script corresponding with the ESB operation flows, after simulation message access queue, each request message in the message access queue carries out service request according to ESB operation flows using ESB service access script to ESB, test result is determined further according to the timestamp recorded during this, due to being the ESB operation flows of simulation, on the one hand it ensure that the data safety of operation system, another side is easy to obtain the relevant information required for testing again, simultaneously, ESB message handling ability is determined by the timestamp of record, improve the accuracy of ESB message handling ability test, it is simultaneously convenient, fast, improve testing efficiency.
According to actual needs, simulation ESB operation flows can have different implementations, here, providing a kind of concrete implementation mode, shown in Figure 2, it comprises the following steps：
Step S1011：Each route in ESB operation flows and target service service are simulated；
Target service is serviced and is simulated, the analog service service needed is generated, starting just can be accessed and be accessed by ESB with the corresponding service server of analog service service, then corresponding analog service service；
Step S1012：The analog service service that the ESB accesses simulation is obtained, according to the analog service service configuration business operation, generates the agency service；
ESB is accessed the analog service service obtained in step S1011 according to business integration demand by way of route；Then configuration service is operated, and business operation refers to that ESB is changed to request using platform feature, filtered, distributed etc. and to operate；It is exactly finally to generate agency service, the agency service is outside access ESB entrance；
Step S1013：The outside access interface of the agency service is provided；
The agency service is released, for extraneous request call.
By the way of this simulation ESB operation flows, with good application prospect, it is beneficial to obtain the relevant information required for follow-up test ESB message handling ability while guaranteeing data security, again.
Shown in Figure 3 in wherein one embodiment, above-mentioned ESB service access scripts of setting up specifically may include steps of：
Step S1021：According to the outside access interface, generation accesses the ESB service access scripts of the agency service；
As it appears from the above, the agency service that ESB is externally issued has corresponding access interface, the script for being able to access that the ESB agency services can be generated by the access interface parse；
Step S1022：Request is added in the ESB service access script and starts affairs, the request starts affairs when each solicited message proceeds by service request, generation global uniqueness mark (GUID, Globally Unique Identifier) corresponding with request message.
Using the scheme in the present embodiment, each solicited message correspond to a global uniqueness mark, the GUID that can be then obtained from every message for including request message, to distinguish request message, simultaneously, GUID and each timestamp can be bound, it is determined that ESB message handling ability when, it is possible to the timestamp of different solicited messages is distinguished by GUID.
According to actual needs, as shown in figure 4, message access queue can be in the following way to ESB progress service requests：
Step S1031：Each request message in the message access queue starts with the ESB service access script and carries out service request to ESB according to the ESB operation flows, and time stab when each request message to be proceeded by service request respectively is initial time stamp；
Each request message is usually that each request message being transmitted in the form of message packet in access, message access queue is typically transmitted access in a synchronous manner, because each message access queue only has first message request MheadThere is the Connection Time, and the non-first message request in message access queue does not have the Connection Time, in order to make a distinction, if request message is Mhead, then GUID value be：MH { GUID value }；Obtained GUID is embedded in message packet carries out message transmission together along with request message；If for example, request message is Soap (Soap refers to simple object access protocol) message request, GUID new records can be added a GUID parameter in the soap heads of message, the form of record is：
<soap：Header>
<GUID>{GUID_VALUE}</GUID>
</soap：Header>
Time stab when recording current is initial time stamp Tstart, the initial time stamp and GUID value binding, such as " { GUID value } ＆Tstart：{TstartValue } ",
Step S1032：Time stab when each solicited message being reached into access target respectively stabs for arrival time；
Access target can refer to foregoing agency service, because operation flow is linked into ESB, then access target can also refer to ESB, or other；
Record timestamp when each solicited message reaches access target and stab T for arrival timereceived, the arrival time is stabbed and GUID value is bound, such as " { GUID value } ＆Treceived：{TreceivedValue } "；
Step S1033：Time stab at the end of each request message is carried out into service request respectively is ending time stamp；
It is ending time stamp, the ending time stamp and GUID value binding, such as " { GUID value } ＆Tend to record the timestamp at the end of each request message carries out service request：{TendValue } ".
It should be noted that in the present embodiment, timestamp is employed from mode that GUID value is bound in the way of distinguishing different solicited messages, in actual applications, however it is not limited to this mode.
In addition, as shown in figure 5, determining that test result can be achieved by the steps of according to the corresponding timestamp of each solicited message of record：
Step S1041：According to TResponse time=Tend-TstartThe response time of each request message is determined, wherein, TResponse timeFor the response time of request message, TendFor ending time stamp, TstartFor initial time stamp；
Step S1042：According to TUser's Connection Time=TThe corresponding time of head message-TThe corresponding time of non-head messageThe Connection Time of the message access queue is determined, wherein, TUser's Connection TimeRefer to the Connection Time of message access queue, TThe corresponding time of head messageFor MheadResponse time, TThe corresponding time of non-head messageRefer to the response time of non-first message request；
In a message queue, only first message request MheadJust there is link time；
Step S1043：According to TMessage processing time=Tend-Tstart-TUser's Connection TimeDetermine the corresponding message processing time of each request message；
Step S1044：Test result is determined according to the response time, the Connection Time, the message processing time；
In order that test result is more accurate, service business request can be entered by multiple message access queues and obtain corresponding response time, Connection Time, message processing time, obtain a number of data sample, the normal operation range of each single item test index is predicted, probability distribution algorithm can be such as used：
Asked by calculating multiple message queues, draw the data sample of certain quantity, predict the normal operation range of each single item test index.Use probability distribution algorithm：
Valid data are chosen, the data that error is accessed in exclusion test are ranked up, it is assumed that had N number of sample, be designated as X1~XN；
The average value of target detection index sample is calculated as desired value, E (X) is designated as
Calculate its standard deviation and show its degree of scatter with desired value, the computing formula of standard deviation is：
If the degree of fluctuation of the standard deviation of the test index is smaller, the desired value E (X) of this test index parameter can be used as basis for estimation for tester.
According to the method for testing of the ESB message handling abilities of the invention described above, the present invention also provides a kind of test system of ESB message handling abilities.The structural representation of the system embodiment of the present invention is shown in Fig. 2.
As shown in Fig. 2 the system in the present embodiment includes：
Service analogue module 201, for simulating ESB operation flows；
Ask performing module 204, for when receiving test instruction, drive each request message in the message access queue to carry out service request to ESB according to the ESB operation flows using the ESB service access script, and record the timestamp on material time node；
In wherein one embodiment, service analogue module 201 can include：
Service analogue unit 2011, for being simulated to each route in ESB operation flows and target service service；
In wherein one embodiment, script generation module 202 can include：
In wherein one embodiment, request performing module will be sent to the service analogue module described in request performing module 203 in the message access queue, and each request message in the message access queue start with the ESB service access script according to the ESB operation flows to ESB carry out service request when, time stab when each request message to be proceeded by service request respectively is initial time stamp, and the time stab at the end of each request message also is carried out into service request respectively is ending time stamp；
Each solicited message is reached access target by service analogue module 201 respectively, when time stab be arrival time stamp；
Wherein, service analogue module 201 is applied not only to foregoing ESB operation flows, simultaneously for receiving request message, and solicited message is handled, each request message is sent to service analogue module 201 by request performing module 204, the request transmission request message of performing module 204 correspond to foregoing each request message and start to carry out service request to ESB, service analogue module 201 receives to receive and asks to correspond to foregoing each solicited message arrival access target, namely access target refers to service analogue module 201, request is returned after the processing of service analogue module 201, request performing module 204 meet with a response result correspond to foregoing each request message terminate to ESB carry out service request.
In wherein one embodiment, data processing module 205 can include：
Response time determining unit 2051, for according to TResponse time=Tend-TstartDetermine the response time of each request message；
Connection Time determining unit 2052, for according to TUser's Connection Time=TThe corresponding time of head message-TThe corresponding time of non-head messageDetermine the Connection Time of the message access queue；
Treatment time determining unit 2053, for according to TMessage processing time=Tend-Tstart-TUser's Connection TimeDetermine the corresponding message processing time of each request message；
Test result obtaining unit 2054, for determining test result according to the response time, the Connection Time, the message processing time；
Wherein, TResponse timeRefer to the response time of request message, TendRefer to request message and terminate to carry out corresponding ending time stamp, T during service requeststartRefer to request message and proceed by corresponding initial time stamp, T during service requestUser's Connection TimeRefer to the Connection Time of message access queue, TThe corresponding time of head messageRefer to the response time of first message request, TThe corresponding time of non-head messageRefer to the response time of non-first message request, TMessage processing timeRefer to the message processing time of request message.
It should be noted that data processing module 205 is in addition to for the calculating of above-mentioned data, it is additionally operable to collect and disposal data, that is, collects and arrange each timestamp etc., will not be described here.
For the ease of understanding said process, illustrated by taking the request process of a message access queue for there are two request messages as an example, it is shown in Figure 7, there is the request process timing diagram of the message access queue of two request messages for one, illustrate the parameters in ESB message handling abilities and calculated relationship when each.T1 is the used time for asking performing module 204 to be returned from the request for starting request to reception, reflects ESB response time, thus, TResponse time=Tend-Tstart；T2 accesses the link time that ESB is consumed by user, there was only first message request M in a message queueheadLink time is just had, so the formula of ESB user's link time is TUser's Connection Time=TThe corresponding time of head message-TThe corresponding time of non-head message, i.e., the response time for subtracting non-first message request using the response time of first message request can be obtained by user's link time in now message queue；T3 is subscription request message treatment time；T5 is that message returns to treatment time；T4 is business service treatment time；Because business service processing is unrelated with ESB platform properties without calculating, being ignored in simulation test business；Request message treatment time T3 formula is：
TRequest message treatment time=Treceived-Tstart-TUser's Connection Time
The T in non-first message requestUser's Connection TimeFor 0, the computing formula that message returns to treatment time T5 is：
TMessage processing time=Tend-Treceived
The computing formula of ESB message processing time is：
TRequest message treatment time=Treceived+TMessage processing time
That is TMessage processing time=Tend-Tstart-TUser's Connection Time。
Embodiment described above only expresses the several embodiments of the present invention, and it describes more specific and detailed, but therefore can not be interpreted as the limitation to the scope of the claims of the present invention.It should be pointed out that for the person of ordinary skill of the art, without departing from the inventive concept of the premise, various modifications and improvements can be made, these belong to protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be determined by the appended claims.
Claims (10)
1. a kind of method of testing of ESB message handling abilities, it is characterised in that comprise the following steps：
Simulate ESB operation flows；
Set up ESB service access script corresponding with the ESB operation flows；
Each request message simulated in message access queue, the message access queue carries out service request according to the ESB operation flows using the ESB service access script to ESB, and records the timestamp on material time node；
Test result is determined according to the corresponding timestamp of each solicited message of record.
2. the method for testing of ESB message handling abilities according to claim 1, it is characterised in that the simulation ESB operation flows include step：
Each route in ESB operation flows and target service service are simulated；
The analog service service that the ESB accesses simulation is obtained, according to the analog service service configuration business operation, generates agency service；
The outside access interface of the agency service is provided.
3. the method for testing of ESB message handling abilities according to claim 2, it is characterised in that foundation ESB service access script corresponding with the ESB operation flows includes step：
According to the outside access interface, generation accesses the ESB service access scripts of the agency service；
Request is added in the ESB service access script and starts affairs, the request starts affairs when each solicited message proceeds by service request, global uniqueness mark corresponding with request message is generated.
4. the method for testing of ESB message handling abilities according to claim 1, it is characterized in that, each request message in the message access queue carries out service request to ESB using the ESB service access script according to the ESB operation flows, and records the timestamp on material time node and include step：
Each request message in the message access queue starts with the ESB service access script and carries out service request to ESB according to the ESB operation flows, and time stab when each request message to be proceeded by service request respectively is initial time stamp；
Time stab when each solicited message being reached into access target respectively stabs for arrival time；
Time stab at the end of each request message is carried out into service request respectively is ending time stamp.
5. the method for testing of ESB message handling abilities according to claim 1, it is characterised in that the corresponding timestamp of each solicited message according to record determines that test result includes step：
According to TResponse time=T3nd-TstartDetermine the response time of each request message；
According to TUser's Connection Time=TThe corresponding time of head message-TThe corresponding time of non-head messageDetermine the Connection Time of the message access queue；
According to TMessage processing time=T3nd-Tstart-TUser's Connection TimeDetermine the corresponding message processing time of each request message；
Test result is determined according to the response time, the Connection Time, the message processing time；
Wherein, TResponse timeRefer to the response time of request message, TendRefer to request message and terminate to carry out corresponding ending time stamp, T during service requeststartRefer to request message and proceed by corresponding initial time stamp, T during service requestUser's Connection TimeRefer to the Connection Time of message access queue, TThe corresponding time of head messageRefer to the response time of first message request in message access queue, TThe corresponding time of non-head messageRefer to the response time of non-first message request in message access queue, TMessage processing timeRefer to the message processing time of request message.
6. a kind of test system of ESB message handling abilities, it is characterised in that including：
Service analogue module, for simulating ESB operation flows；
Script generation module, for setting up ESB service access script corresponding with the ESB operation flows；
Message Simulation module, for simulating message access queue；
Performing module is asked, for when receiving test instruction, driving each request message in the message access queue to carry out service request to ESB according to the ESB operation flows using the ESB service access script, and the timestamp on material time node is recorded；
Data processing module, test result is determined for the corresponding timestamp of each solicited message according to record.
7. the test system of ESB message handling abilities according to claim 6, it is characterised in that the service analogue module includes：
Service analogue unit, for being simulated to the route in ESB operation flows and target service service；
Dispensing unit, for the ESB to be accessed into the analog service service that simulation is obtained, according to the analog service service configuration business operation, generates the agency service；
Interface unit, the outside access interface for providing the agency service.
8. the test system of ESB message handling abilities according to claim 7, it is characterised in that the script generation module includes：
Script generation unit, for according to the outside access interface, generation to access the ESB service access scripts of the agency service；
Unit is identified, starts affairs for adding request in the ESB service access script, the request starts affairs when each solicited message proceeds by service request, global uniqueness mark corresponding with request message is generated.
9. the test system of ESB message handling abilities according to claim 6, it is characterised in that：
The request performing module will be sent to the service analogue module in the message access queue, and each request message in the message access queue start with the ESB service access script according to the ESB operation flows to ESB carry out service request when, time stab when each request message to be proceeded by service request respectively is initial time stamp, and the time stab at the end of each request message also is carried out into service request respectively is ending time stamp；
Time stab when each solicited message is reached the service analogue module by the service analogue module respectively stabs for arrival time.
10. the test system of ESB message handling abilities according to claim 6, it is characterised in that the data processing module includes：
Response time determining unit, for according to TResponse time=Tend-TstartDetermine the response time of each request message；
Connection Time determining unit, for according to TUser's Connection Time=TThe corresponding time of head message-TThe corresponding time of non-head messageDetermine the Connection Time of the message access queue；
Treatment time determining unit, for according to TMessage processing time=Tend-Tstart-TUser's Connection TimeDetermine the corresponding message processing time of each request message；
Test result obtaining unit, for determining test result according to the response time, the Connection Time, the message processing time；
Wherein, TResponse timeRefer to the response time of request message, T3ndRefer to request message and terminate to carry out corresponding ending time stamp, T during service requeststartRefer to request message and proceed by corresponding initial time stamp, T during service requestUser's Connection TimeRefer to the Connection Time of message access queue, TThe corresponding time of head messageRefer to the response time of first message request in message access queue, TThe corresponding time of non-head messageRefer to the response time of non-first message request in message access queue, TMessage processing timeRefer to the message processing time of request message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310135106.8A CN103218295B (en) | 2013-04-17 | 2013-04-17 | The method of testing of ESB message handling ability and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310135106.8A CN103218295B (en) | 2013-04-17 | 2013-04-17 | The method of testing of ESB message handling ability and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103218295A true CN103218295A (en) | 2013-07-24 |
| CN103218295B CN103218295B (en) | 2016-02-24 |
Family
ID=48816113
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310135106.8A Active CN103218295B (en) | 2013-04-17 | 2013-04-17 | The method of testing of ESB message handling ability and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103218295B (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104517606A (en) * | 2013-09-30 | 2015-04-15 | 腾讯科技（深圳）有限公司 | Method and device for recognizing and testing speech |
| CN105701000A (en) * | 2014-11-25 | 2016-06-22 | 中兴通讯股份有限公司 | Service testing method and device |
| CN106546902A (en) * | 2016-10-13 | 2017-03-29 | 芯海科技（深圳）股份有限公司 | A kind of volume production method of testing of OTP types MCU in the case of test interface is not reserved |
| CN107423893A (en) * | 2017-07-19 | 2017-12-01 | 北京京东尚科信息技术有限公司 | The all standing method of testing and device of a kind of operation flow |
| CN105988932B (en) * | 2015-05-13 | 2018-10-16 | 中国银联股份有限公司 | A kind of test method and system of ESB |
| CN111143081A (en) * | 2018-11-05 | 2020-05-12 | 马上消费金融股份有限公司 | Performance evaluation method and device |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020053043A1 (en) * | 2000-10-27 | 2002-05-02 | Friedman George E. | Enterprise test system having program flow recording and playback |
| CN101819551A (en) * | 2009-02-27 | 2010-09-01 | 国际商业机器公司 | Method and system for recording service interaction data of enterprise message system |
-
2013
- 2013-04-17 CN CN201310135106.8A patent/CN103218295B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020053043A1 (en) * | 2000-10-27 | 2002-05-02 | Friedman George E. | Enterprise test system having program flow recording and playback |
| CN101819551A (en) * | 2009-02-27 | 2010-09-01 | 国际商业机器公司 | Method and system for recording service interaction data of enterprise message system |
Non-Patent Citations (1)
| Title |
|---|
| 华竹轩 等: "基于企业服务总线中间件的评估模型", 《计算机工程》 * |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104517606A (en) * | 2013-09-30 | 2015-04-15 | 腾讯科技（深圳）有限公司 | Method and device for recognizing and testing speech |
| CN105701000A (en) * | 2014-11-25 | 2016-06-22 | 中兴通讯股份有限公司 | Service testing method and device |
| CN105701000B (en) * | 2014-11-25 | 2019-05-07 | 中兴通讯股份有限公司 | Service test method and device |
| CN105988932B (en) * | 2015-05-13 | 2018-10-16 | 中国银联股份有限公司 | A kind of test method and system of ESB |
| CN106546902A (en) * | 2016-10-13 | 2017-03-29 | 芯海科技（深圳）股份有限公司 | A kind of volume production method of testing of OTP types MCU in the case of test interface is not reserved |
| CN107423893A (en) * | 2017-07-19 | 2017-12-01 | 北京京东尚科信息技术有限公司 | The all standing method of testing and device of a kind of operation flow |
| CN111143081A (en) * | 2018-11-05 | 2020-05-12 | 马上消费金融股份有限公司 | Performance evaluation method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103218295B (en) | 2016-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103218295A (en) | Method and system for testing message handling capacity of ESB (Enterprise Service Bus) | |
| CN101616174B (en) | Method for optimizing system performance by dynamically tracking IO processing path of storage system | |
| US8171133B2 (en) | Management apparatus and management method for computer system | |
| CN103678093B (en) | A kind of automated test frame and method of testing | |
| US10409251B2 (en) | Automatic inspection and monitoring method based on time domain slotting control | |
| CN104461903B (en) | The method and apparatus of test client based on browser | |
| CN101322113B (en) | Grid computing control method for testing application program capacity of server and service method thereof | |
| CN101399715B (en) | Network test platform and test method for optical fiber channel | |
| CN103178998A (en) | Test and control data transmission method and device | |
| US10057155B2 (en) | Method and apparatus for determining automatic scanning action | |
| CN109656799A (en) | Test method and device | |
| CN110019386A (en) | A kind of stream data processing method and equipment | |
| CN108243033A (en) | A kind of method given a mark to video quality, cloud server terminal and system | |
| CN108964822B (en) | Method and system for acquiring network time in parallel by multiple schemes | |
| CN109815102B (en) | Test data statistical method, device and storage medium | |
| US20180288636A1 (en) | A method for automatic measurement of App load power consumption on mobile devices based on physical measurement | |
| CN103684823A (en) | Weblog recording method, network access path determining method and related devices | |
| CN113067802B (en) | User identification method, device, equipment and computer readable storage medium | |
| CN102043594A (en) | System and method for realizing collection and playback of input/output trace under distribution environment | |
| CN107888690A (en) | The statistical method and system of response time | |
| CN108280024A (en) | Traffic distribution strategy test method, device and electronic equipment | |
| Bause et al. | SDL and Petri net performance analysis of communicating systems | |
| CN106899550B (en) | Cloud platform resource monitoring method and device | |
| CN110633182B (en) | System, method and device for monitoring server stability | |
| CN107786292A (en) | A kind of measuring method and device of protocol stack network time |
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 | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 510080 Dongfeng East Road, Dongfeng, Guangdong, Guangzhou, Zhejiang Province, No. 8 Patentee after: ELECTRIC POWER RESEARCH INSTITUTE, GUANGDONG POWER GRID CO., LTD. Address before: 510080 Dongfeng East Road, Dongfeng, Guangdong, Guangzhou, Zhejiang Province, No. 8 Patentee before: Electrical Power Research Institute of Guangdong Power Grid Corporation |
|
| CP01 | Change in the name or title of a patent holder |