CN103297295B - The method of testing of the communication mode of ESB and test macro - Google Patents
The method of testing of the communication mode of ESB and test macro Download PDFInfo
- Publication number
- CN103297295B CN103297295B CN201310200395.5A CN201310200395A CN103297295B CN 103297295 B CN103297295 B CN 103297295B CN 201310200395 A CN201310200395 A CN 201310200395A CN 103297295 B CN103297295 B CN 103297295B
- Authority
- CN
- China
- Prior art keywords
- request
- communication
- service
- esb
- asynchronous
- 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.)
- Active
Links
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides method of testing and the system of the communication mode of a kind of ESB, its method comprises step: receive the type instruction being used for communication mode test; On ESB, the communication service corresponding with the type instruction is registered according to described type instruction; Send request sequence by described ESB to described communication service, described request sequence comprises service request corresponding to plural and described type instruction; Receive the response results of each described service request of described communication service response that described ESB returns; The response results corresponding according to each described service request judges whether described ESB supports the communication mode corresponding with described type instruction, and the present invention can improve testing efficiency and the accuracy of the communication mode of ESB.
Description
Technical field
The present invention relates to software performance test, particularly relate to method of testing and the test macro of the communication mode of a kind of ESB.
Background technology
ESB (EnterpriseServiceBus, ESB) make use of multiple generally acknowledged, the ripe and reliable communication technology, supports the communication of upper layer data transmission.At CORBA (CommonObjectRequestBrokerArchitecture, Common Object Request Broker Architecture/CORBA) and JMS (JavaMessageService, Java messenger service) technology basis on, ESB can support synchronous communication, asynchronous communication simultaneously.
For this communication mode of asynchronous communication, plurality of communication schemes innovatively combines together by ESB, comprising point-to-point communication pattern (Point-to-Point), publish/subscribe communication pattern (Publish-Subscribe), and support the important leverage function such as encryption, compression, breakpoint transmission in communication process.
But, point-to-point, point-to-multipoint is the application integration solution of earliest period, it to need in enterprise to exchange information, share data system between two bridge joint get up, the technology of bridge joint is also for two particular system custom-made communication links are to change the interface of these two systems, the difference such as agreement and data format.Its shortcoming is apparent.First, when connecting aggravation, being difficult to safeguard, and the demand tackling business change at any time cannot be met; Its two, the demand of system interconnected communication between two can only be met, the complex business process relating to multiple application system cannot be realized.
In addition, ESB supports that synchronous communication and asynchronous communication need the realization of Various Complex technology.The different degree of support of ESB product to different communication modes is also not quite similar.The test of the communication mode of ESB whether ESB product is had to one of important measures that asynchronous/synchronous communication ability judges, for tester understand ESB asynchronous/synchronous communication ability plays an important role.The test mode of the communication mode of current ESB is only tested for specific ESB product, specific communication mode.But, the ESB product property of there are differences of each manufacturer, the communication mode of ESB product support also also exists otherness, when testing, tester is needed to write different testing tools, to realize different service logics, which adds a lot of extra work amount, also may bring extra risk of errors due to the problem of writing of testing tool, therefore, seriously reduce testing efficiency and the accuracy of communication mode.
Summary of the invention
The object of the present invention is to provide method of testing and the test macro of the communication mode of a kind of ESB, testing efficiency and accuracy can be improved.
Object of the present invention is achieved through the following technical solutions:
A method of testing for the communication mode of ESB, comprises the steps:
Receive the type instruction being used for communication mode test;
On ESB, the communication service corresponding with the type instruction is registered according to described type instruction;
Send request sequence by described ESB to described communication service, described request sequence comprises service request corresponding to plural and described type instruction;
Receive the response results of each described service request of described communication service response that described ESB returns;
The response results corresponding according to each described service request judges whether described ESB supports the communication mode corresponding with described type instruction.
A test macro for ESB communication mode, comprising:
Command reception module, for receiving the type instruction for communication mode test;
Registering modules, for registering the communication service corresponding with the type instruction according to described type instruction on ESB;
Request module, for sending request sequence by described ESB to described communication service, described request sequence comprises service request corresponding to plural and described type instruction;
Result receiver module, for receiving the response results of each described service request of described communication service response that described ESB returns;
For the response results corresponding according to each described service request, judge module, judges whether described ESB supports the communication mode corresponding with described type instruction.
According to the scheme of the invention described above, after it receives the type instruction for communication mode test, on ESB, corresponding communication service is registered based on the type instruction, and send request sequence by described ESB to described communication service based on the type instruction, described request sequence comprises service request corresponding to two or more, receive the response results of each described service request of described communication service response that described ESB returns, and the response results corresponding according to each described service request judges whether ESB supports corresponding communication mode, owing to being send request sequence to this communication service after registering communication service on ESB, after receiving the response results of each described service request in this communication service response request sequence, judge based on response results, communication mode for different product E SB same types can by testing after the same communication service of registration, while reducing the workload of tester, improve testing efficiency, simultaneously, the communication mode whether ESB is corresponding is judged by the response results that service request is corresponding, convenient and swift, and accuracy is high, and, the type of different communication mode tests can be set according to actual needs, such as synchronous communication, asynchronous communication, to meet the needs of different communication mode tests, testing efficiency is high.
Accompanying drawing explanation
Fig. 1 is the schematic flow sheet of the method for testing embodiment of the communication mode of ESB of the present invention;
Fig. 2 is the schematic flow sheet that the inventive method carries out an embodiment of the test of synchronous communication;
Fig. 3 is the schematic flow sheet that the inventive method carries out another embodiment of the test of synchronous communication;
Fig. 4 is the schematic flow sheet that the inventive method carries out the embodiment of the test of asynchronous communication;
Fig. 5 is the structural representation of the test macro embodiment of the communication mode of ESB of the present invention.
Embodiment
Below in conjunction with embodiment and accompanying drawing, the present invention is further elaborated, but implementation of the present invention is not limited thereto.
Shown in Figure 1, be the schematic flow sheet of the method for testing embodiment of the communication mode of ESB of the present invention.As shown in Figure 1, the method for testing of the communication mode of the ESB in the present embodiment comprises the steps:
Step S101: receive the type instruction being used for communication mode test;
Step S102: register the communication service corresponding with the type instruction according to described type instruction on ESB;
Any one attainable mode existing can be adopted in the mode of ESB registering communication service, not repeat them here;
Step S103: send request sequence to described communication service by described ESB, described request sequence comprises service request corresponding to plural and described type instruction;
Multiple service request is generally comprised in request sequence, such as one request sequence comprising service request 1, service request 2, service request 3...... service request n, for the ease of analyzing responding result, the time interval of adjacent service request in request sequence should be little as far as possible, and its time (terminating to the response results receiving this service request from sending service request) completing a service request relative to a service request can be ignored;
Step S104: the response results receiving each described service request of described communication service response that described ESB returns;
In step s 103 by request sequence through described ESB after communication service, service request in this communication service meeting response request sequence, service request is processed, response results is returned through ESB again after process terminates, response results can comprise different information according to the difference of business, but the time point generally comprising content information and return;
Step S105: the response results corresponding according to each described service request judges whether described ESB supports the communication mode corresponding with described type instruction;
Judge whether ESB supports synchronous communication/asynchronous communication according to response results, its judgment mode can adopt the mode that can realize arbitrarily, such as adopt the mode whether receiving the response results of the service request of interior correspondence in special time, or the mode that whether corresponding with type instruction the processing time having adopted the time of each service request processing procedure in request sequence be consistent, or the mode of whether corresponding with the type instruction sequence consensus of the sequential time receiving each service request etc.
Accordingly, according to the scheme in above-mentioned the present embodiment, after it receives the type instruction for communication mode test, on ESB, corresponding communication service is registered based on the type instruction, and send request sequence by described ESB to described communication service based on the type instruction, described request sequence comprises service request corresponding to two or more, receive the response results of each described service request of described communication service response that described ESB returns, and the response results corresponding according to each described service request judges whether ESB supports corresponding communication mode, owing to being send request sequence to this communication service after registering communication service on ESB, after receiving the response results of each described service request in this communication service response request sequence, judge based on response results, communication mode for different product E SB same types can by testing after the same communication service of registration, while reducing the workload of tester, improve testing efficiency, simultaneously, the communication mode whether ESB is corresponding is judged by the response results that service request is corresponding, convenient and swift, and accuracy is high, and, according to actual needs, the type of different communication mode tests can be set, such as synchronous communication, asynchronous communication, to meet the needs of different communication mode tests, testing efficiency is high.
For the ease of judging whether described ESB supports the communication mode corresponding with described type instruction, wherein in an embodiment, the method of testing of the communication mode of ESB of the present invention, can also comprise step: the request treatment cycle that described service request carries out service request is set, described request treatment cycle is greater than the time interval in request sequence between adjacent service request, wherein, request treatment cycle refers to that a service request completes the time of a service request (terminating to the response results receiving this service request from sending service request), as previously mentioned, request treatment cycle should be larger as much as possible than the time interval in request sequence between adjacent service request, the time interval can be ignored relative to request treatment cycle, judge whether described ESB supports the communication mode corresponding with described type instruction based on information such as this request treatment cycle and the time points returning response results, convenient and swift, and accuracy is high.
As mentioned above, according to actual needs, the type of different communication mode tests can be set, to meet the needs of different communication mode tests.Test mode below in conjunction with synchronous communication wherein, asynchronous communication is described in detail.
To carry out the test of synchronous communication in Fig. 2, show in one of them embodiment the schematic flow sheet that the synchronous communication of ESB is tested.
As shown in Figure 2, when carrying out the test of synchronous communication, concrete process can be:
Step S201: receive the synchronous communication test instruction being used for synchronous communication test, the type instruction namely in above-described embodiment is synchronous communication test instruction;
Step S202: register synchronization request service according to described type instruction on ESB, the communication service corresponding with type instruction namely in above-described embodiment is synchronization request service;
Step S203: send request sequence through described ESB to described synchronization request service, described request sequence comprises two or more synchronization request, the service request corresponding with type instruction namely in above-described embodiment is synchronization request;
Step S204: the response results receiving each described synchronization request of described synchronization request service response that described ESB returns;
Step S205: determine the time of reception point receiving each described synchronization request according to the response results of each described synchronization request, the reception order of the response results receiving each described synchronization request is determined according to the time of reception point of the correspondence of each described synchronization request, judge whether described ESB supports synchronous communication according to described reception order, the communication mode corresponding with type instruction namely in above-described embodiment is synchronous communication.
Wherein, when judging whether ESB supports synchronous communication, it is the time of reception point (time of reception) first determining to receive each described synchronization request, namely correspond to each synchronization request and have a time of reception point, reception order is determined again according to this time of reception point, judge whether ESB supports synchronous communication based on this reception order, such as, synchronization request in request sequence is according to synchronization request 1, synchronization request 2, the order of synchronization request 3...... synchronization request n, if the order receiving response results is also according to synchronization request 1, synchronization request 2, the order of synchronization request 3...... synchronization request n, then can be judged to be that ESB supports synchronous communication, otherwise then ESB does not support synchronous communication.
Also be carry out the test of synchronous communication for example in Fig. 3, show in another embodiment the schematic flow sheet that the synchronous communication of ESB is tested, step S301 in the present embodiment ~ step S304 is corresponding identical with the step S201 ~ step S204 in a upper embodiment, do not repeat them here, its difference is to judge whether ESB supports the mode of synchronous communication, only describe this processing procedure, as follows:
Step S305: determine the time of reception point receiving each described synchronization request according to the response results of each described synchronization request, total request processing time of each synchronization request in request sequence has been determined according to the time of reception point of each described synchronization request, according to always asking the number of synchronization request in processing time, request treatment cycle, described request sequence to judge whether described ESB supports synchronous communication according to described reception order, the communication mode corresponding with type instruction namely in above-described embodiment is synchronous communication.
In the present embodiment, when judging whether ESB supports synchronous communication, it is the time of reception point (time of reception) first determining to receive each described synchronization request, determine always to ask the processing time according to this time of reception point again, finally always ask processing time and request treatment cycle based on this, in described request sequence, the number of synchronization request judges whether ESB supports synchronous communication, wherein, determine always to ask the processing time can have different implementations according to time of reception point, such as, adopt always ask processing time=mode of (time point that time point-the first response results corresponding to last response results is corresponding)+request treatment cycle, also can be other any reasonable manners, processing time and request treatment cycle is always asked based on this, in described request sequence, the number of synchronization request judges whether ESB supports synchronous communication, can be always to ask the product of processing time with the number of asking treatment cycle and synchronization request to contrast, if identical or in preset range, then can be judged to be that ESB supports synchronous communication, wherein, identically refer in the situation ignoring the time interval between synchronization request, in preset range, it is the situation in the time interval considered between synchronization request.
Above-mentioned two embodiments one judge whether ESB supports synchronous communication based on reception order, one is judge whether ESB supports synchronous communication based on total request processing time, also can Integrated Receiver order, total request processing time judges whether ESB supports synchronous communication, do not repeat them here, also other modes that can realize arbitrarily can be adopted, continuous print time of reception section is such as set, and the sequence number that should receive the synchronization request of response results in each time of reception section is preset according to the order of synchronization request in request sequence, if have received the response results of synchronization request corresponding to default sequence number in each time period, then can be judged to be that described ESB supports synchronous communication, otherwise be judged to be that ESB does not support synchronous communication.
To carry out the test of asynchronous communication in Fig. 4, show the schematic flow sheet that the asynchronous communication of ESB is tested.
As shown in Figure 4, when carrying out the test of asynchronous communication, concrete process can be:
Step S401: receive the asynchronous communication test instruction being used for asynchronous communication test, the type instruction namely in above-described embodiment is asynchronous communication test instruction;
Step S402: register Asynchronous Request service according to described type instruction on ESB, the communication service corresponding with type instruction namely in above-described embodiment is Asynchronous Request service;
Step S403: send request sequence through described ESB to described Asynchronous Request service, described request sequence comprises two or more Asynchronous Request, the service request corresponding with type instruction namely in above-described embodiment is Asynchronous Request;
Step S404: the response results receiving each described Asynchronous Request of described Asynchronous Request service response that described ESB returns;
Step S405: determine the time of reception point receiving each described Asynchronous Request according to the response results of each described Asynchronous Request, total request processing time of each Asynchronous Request in request sequence has been determined according to the time of reception point of each described Asynchronous Request, according to always asking the processing time, request process week judging whether described ESB supports asynchronous communication, the communication mode corresponding with type instruction namely in above-described embodiment is asynchronous communication.
In the present embodiment, when judging whether ESB supports asynchronous communication, it is the time of reception point (time of reception) first determining to receive each described Asynchronous Request, determine always to ask the processing time according to this time of reception point again, finally always ask processing time and request treatment cycle based on this, in described request sequence, the number of Asynchronous Request judges whether ESB supports asynchronous communication, wherein, determine always to ask the processing time can have different implementations according to time of reception point, such as, adopt always ask processing time=mode of (time point that time point-the first response results corresponding to last response results is corresponding)+request treatment cycle, also can be other any reasonable manners, processing time and request treatment cycle is always asked based on this, in described request sequence, the number of Asynchronous Request judges whether ESB supports asynchronous communication, can be always to ask the processing time to contrast with request treatment cycle, if identical or in preset range, then can be judged to be that ESB supports asynchronous communication, wherein, identically refer in the situation ignoring the time interval between Asynchronous Request, in preset range, it is the situation in the time interval considered between Asynchronous Request.
It should be noted that, according to different testing requirements, type instruction can be synchronous communication test instruction, also can be asynchronous communication test instruction.
According to the method for testing of the ESB communication mode of the invention described above, the present invention also provides a kind of test macro of ESB communication mode.
Shown in 5, it is the schematic flow sheet of the test macro embodiment of ESB communication mode of the present invention.For convenience of explanation, illustrate only the part relevant to the embodiment of the present invention.
As shown in Figure 5, the test macro of the ESB communication mode in the embodiment of the present invention comprises command reception module 501, Registering modules 502, request module 503, result receiver module 504, judge module 505, wherein:
Command reception module 501, for receiving the type instruction for communication mode test;
Registering modules 502, for registering the communication service corresponding with the type instruction according to described type instruction on ESB;
Request module 503, for sending request sequence by described ESB to described communication service, described request sequence comprises service request corresponding to plural and described type instruction;
Result receiver module 504, for receiving the response results of each described service request of described communication service response that described ESB returns;
For the response results corresponding according to each described service request, judge module 505, judges whether described ESB supports the communication mode corresponding with described type instruction.
Wherein in an embodiment, request module 503 can also be used for arranging the request treatment cycle that described service request carries out service request, and described request treatment cycle is greater than the time interval in request sequence between adjacent service request.
Wherein in an embodiment, as shown in Figure 5, judge module 505 can comprise the first judging unit 501, wherein,
First judging unit 501 is for being synchronous communication test instruction in described type instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, when the communication mode corresponding with described synchronous communication test instruction is synchronous communication, the time of reception point receiving each described synchronization request is determined according to the response results of each described synchronization request, the reception order of the response results receiving each described synchronization request is determined according to the time of reception point of the correspondence of each described synchronization request, judge whether described ESB supports synchronous communication according to described reception order.
Wherein in an embodiment, as shown in Figure 5, judge module 505 can comprise the first judging unit 501 and/or the second judging unit 502, wherein:
First judging unit 501 is for being synchronous communication test instruction in described type instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, when the communication mode corresponding with described synchronous communication test instruction is synchronous communication, the time of reception point receiving each described synchronization request is determined according to the response results of each described synchronization request, the reception order of the response results receiving each described synchronization request is determined according to the time of reception point of the correspondence of each described synchronization request, judge whether described ESB supports synchronous communication according to described reception order, or for being synchronous communication test instruction in described type instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, when the communication mode corresponding with described synchronous communication test instruction is synchronous communication, the time of reception point receiving each described synchronization request is determined according to the response results of each described synchronization request, total request processing time of each synchronization request in request sequence has been determined according to the time of reception point of each described synchronization request, according to always asking the processing time, request treatment cycle, in described request sequence, the number of synchronization request judges whether described ESB supports synchronous communication,
Second judging unit 502 is for being asynchronous communication test instruction in described type instruction, the communication service corresponding with described asynchronous communication test instruction is Asynchronous Request service, the service request corresponding with described asynchronous communication test instruction is Asynchronous Request, when the communication mode corresponding with described asynchronous communication test instruction is asynchronous communication, the time of reception point receiving each described Asynchronous Request is determined according to the response results of each described Asynchronous Request, total request processing time of each Asynchronous Request in request sequence has been determined according to the time of reception point of each described Asynchronous Request, according to always asking the processing time, request treatment cycle judges whether described ESB supports asynchronous communication.
The specific implementation of each module, unit etc. in present system, can identical with the invention described above method, will not repeat in detail at this.
The above embodiment only have expressed several execution mode of the present invention, and it describes comparatively concrete and detailed, but therefore can not be interpreted as the restriction 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, can also make some distortion and improvement, these all belong to protection scope of the present invention.Therefore, the protection range of patent of the present invention should be as the criterion with claims.
Claims (9)
1. a method of testing for the communication mode of ESB, is characterized in that, comprises the steps:
Receive the type instruction being used for communication mode test;
On ESB, the communication service corresponding with the type instruction is registered according to described type instruction;
Send request sequence by described ESB to described communication service, described request sequence comprises service request corresponding to plural and described type instruction;
Receive the response results of each described service request of described communication service response that described ESB returns;
The response results corresponding according to each described service request judges whether described ESB supports the communication mode corresponding with described type instruction.
2. the method for testing of the communication mode of ESB according to claim 1, it is characterized in that, also comprise step: arrange the request treatment cycle that described service request carries out service request, described request treatment cycle is greater than the time interval in request sequence between adjacent service request.
3. the method for testing of the communication mode of ESB according to claim 1 and 2, is characterized in that:
Described type instruction is synchronous communication test instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, and the communication mode corresponding with described synchronous communication test instruction is synchronous communication;
The response results corresponding according to each described service request judges whether described ESB supports that the mode of the communication mode corresponding with described type instruction comprises: determine according to the response results of each described synchronization request the time of reception point receiving each described synchronization request, determine the reception order of the response results receiving each described synchronization request according to the time of reception point of the correspondence of each described synchronization request, judge whether described ESB supports synchronous communication according to described reception order.
4. the method for testing of the communication mode of ESB according to claim 2, is characterized in that:
Described type instruction is synchronous communication test instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, and the communication mode corresponding with described synchronous communication test instruction is synchronous communication;
The response results corresponding according to each described service request judges whether described ESB supports that the mode of the communication mode corresponding with described type instruction comprises: determine according to the response results of each described synchronization request the time of reception point receiving each described synchronization request, determining total request processing time of each synchronization request in request sequence according to the time of reception point of each described synchronization request, having judged whether described ESB supports synchronous communication according to always asking the number of synchronization request in processing time, request treatment cycle, described request sequence.
5. the method for testing of the communication mode of ESB according to claim 2, is characterized in that:
Described type instruction is asynchronous communication test instruction, the communication service corresponding with described asynchronous communication test instruction is Asynchronous Request service, the service request corresponding with described asynchronous communication test instruction is Asynchronous Request, and the communication mode corresponding with described asynchronous communication test instruction is asynchronous communication;
The response results corresponding according to each described service request judges whether described ESB supports that the mode of the communication mode corresponding with described type instruction comprises: determine according to the response results of each described Asynchronous Request the time of reception point receiving each described Asynchronous Request, total request processing time of each Asynchronous Request in request sequence has been determined, according to always asking the processing time, asking treatment cycle to judge whether described ESB supports asynchronous communication according to the time of reception point of each described Asynchronous Request.
6. a test macro for the communication mode of ESB, is characterized in that, comprising:
Command reception module, for receiving the type instruction for communication mode test;
Registering modules, for registering the communication service corresponding with the type instruction according to described type instruction on ESB;
Request module, for sending request sequence by described ESB to described communication service, described request sequence comprises service request corresponding to plural and described type instruction;
Result receiver module, for receiving the response results of each described service request of described communication service response that described ESB returns;
For the response results corresponding according to each described service request, judge module, judges whether described ESB supports the communication mode corresponding with described type instruction.
7. the test macro of the communication mode of ESB according to claim 6, it is characterized in that, described request module also carries out the request treatment cycle of service request for arranging described service request, described request treatment cycle is greater than the time interval in request sequence between adjacent service request.
8. the test macro of the communication mode of ESB according to claim 6, is characterized in that, described judge module comprises the first judging unit;
Described first judging unit, for being synchronous communication test instruction in described type instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, when the communication mode corresponding with described synchronous communication test instruction is synchronous communication, the time of reception point receiving each described synchronization request is determined according to the response results of each described synchronization request, the reception order of the response results receiving each described synchronization request is determined according to the time of reception point of the correspondence of each described synchronization request, judge whether described ESB supports synchronous communication according to described reception order.
9. the test macro of the communication mode of ESB according to claim 7, is characterized in that, described judge module comprises the first judging unit and/or the second judging unit;
It is synchronous communication test instruction that described first judging unit is used in described type instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, when the communication mode corresponding with described synchronous communication test instruction is synchronous communication, the time of reception point receiving each described synchronization request is determined according to the response results of each described synchronization request, the reception order of the response results receiving each described synchronization request is determined according to the time of reception point of the correspondence of each described synchronization request, judge whether described ESB supports synchronous communication according to described reception order, or for being synchronous communication test instruction in described type instruction, the communication service corresponding with described synchronous communication test instruction is synchronization request service, the service request corresponding with described synchronous communication test instruction is synchronization request, when the communication mode corresponding with described synchronous communication test instruction is synchronous communication, the time of reception point receiving each described synchronization request is determined according to the response results of each described synchronization request, total request processing time of each synchronization request in request sequence has been determined according to the time of reception point of each described synchronization request, according to always asking the processing time, request treatment cycle, in described request sequence, the number of synchronization request judges whether described ESB supports synchronous communication,
It is asynchronous communication test instruction that described second judging unit is used in described type instruction, the communication service corresponding with described asynchronous communication test instruction is Asynchronous Request service, the service request corresponding with described asynchronous communication test instruction is Asynchronous Request, when the communication mode corresponding with described asynchronous communication test instruction is asynchronous communication, the time of reception point receiving each described Asynchronous Request is determined according to the response results of each described Asynchronous Request, total request processing time of each Asynchronous Request in request sequence has been determined according to the time of reception point of each described Asynchronous Request, according to always asking the processing time, request treatment cycle judges whether described ESB supports asynchronous communication.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310200395.5A CN103297295B (en) | 2013-05-24 | 2013-05-24 | The method of testing of the communication mode of ESB and test macro |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310200395.5A CN103297295B (en) | 2013-05-24 | 2013-05-24 | The method of testing of the communication mode of ESB and test macro |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103297295A CN103297295A (en) | 2013-09-11 |
| CN103297295B true CN103297295B (en) | 2016-04-27 |
Family
ID=49097640
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310200395.5A Active CN103297295B (en) | 2013-05-24 | 2013-05-24 | The method of testing of the communication mode of ESB and test macro |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103297295B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102347983A (en) * | 2011-08-26 | 2012-02-08 | 四川长虹电器股份有限公司 | ESB (Enterprise Service Bus) system in SOA (Service-Oriented Architecture) |
| CN102364921A (en) * | 2011-11-21 | 2012-02-29 | 携程计算机技术（上海）有限公司 | Realization method and equipment for enterprise service bus and corresponding platform |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8046195B2 (en) * | 2008-08-26 | 2011-10-25 | Red Hat, Inc. | Performance testing of enterprise service bus |
| US9104803B2 (en) * | 2011-01-03 | 2015-08-11 | Paypal, Inc. | On-demand software test environment generation |
-
2013
- 2013-05-24 CN CN201310200395.5A patent/CN103297295B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102347983A (en) * | 2011-08-26 | 2012-02-08 | 四川长虹电器股份有限公司 | ESB (Enterprise Service Bus) system in SOA (Service-Oriented Architecture) |
| CN102364921A (en) * | 2011-11-21 | 2012-02-29 | 携程计算机技术（上海）有限公司 | Realization method and equipment for enterprise service bus and corresponding platform |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103297295A (en) | 2013-09-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103856361A (en) | Method and system for realizing remote debugging | |
| CN102967815B (en) | Chip testing method, automated testing equipment and system | |
| CN103139157B (en) | A kind of based on the network communication method of socket, Apparatus and system | |
| CN102393738A (en) | Diagnostic device and test method of automobile electronic control unit (ECU) | |
| CN102193058A (en) | Test apparatus and test module | |
| CN103441861A (en) | Method and device for generating data records | |
| CN108123826B (en) | Cross-region data interaction system and method | |
| CN109194430A (en) | A kind of C6678 distribution type system time synchronous method and system based on SRIO | |
| CN105024873A (en) | Protocol conformance testing system and method based on equipment and scene simulation | |
| CN102664755B (en) | Control channel fault determining method and device | |
| CN102694692A (en) | Fault detecting method and device of distributed equipment | |
| CN1719415A (en) | Method and system for management of a scalable computer system | |
| CN116436540A (en) | LED display screen receiving card testing method and device, testing card and storage medium | |
| CN101309184A (en) | Method and apparatus detecting failure of micro-engine | |
| CN103297295B (en) | The method of testing of the communication mode of ESB and test macro | |
| CN103106177B (en) | Interconnect architecture and method thereof on the sheet of multi-core network processor | |
| CN104639379A (en) | Proxy testing method and device | |
| CN109274763B (en) | Information synchronization method and dual-computer hot standby equipment | |
| CN111490912A (en) | FPGA-based multichannel signal transmission reliability detection system and method | |
| CN103425583B (en) | The tracking of a kind of multi-DSP parallel system and back method | |
| CN102647686B (en) | For testing testing equipment and the message display method thereof of mobile communication terminal | |
| CN106937319B (en) | Antenna fault self-checking method of wireless equipment | |
| WO2017197829A1 (en) | Test information management method and apparatus, and test case execution system and device | |
| CN115657646A (en) | Test method and device of CAN controller | |
| CN115567400A (en) | Whole cabinet management method, device, equipment and medium |
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 | ||
| 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 |