Hello, Thank you very much for your reply. I really appreciate it. :) *Why do we need to send the meaningful messages into Queue.* In most of the testing scenarios, like performance harness testing. We need the barrage of messages for the testing. If those barrage of messages are meaningful with "randomized valid string" in it then we can have functionality testing + performance harness testing together. Currently JMeter can send the message given by user moreover it has no randomized factor in it. Thus, We can not have full fledged functionality testing on the Middleware Applications. For Example: Consider a Middleware Appplication having Remote Queue ABC which has the following simple XML as meaningful message. This message is further picked up from the ABC by middleware application or API. <msg> <user>XYZ</user> <type>Regular<type> <error_code_reported>123</error_code_reported> <error_type>FATAL</error_type> </msg>
If we send 1000 of such messages then it would test the functionality of the application for type Regular, errorcode 123, errortype FATAL. *My idea is to implement the new "Content Formatting Language" using String grammar and Automata which can generate the all possible cases of <msg> and eventually testing the application thoroughly. I think, this matches with the point 3.2 in the previous mail in this thread by sir *nabarun.mondal. (Thank you very much) *Approach:* This *"Content Formatting Language" *will be having en enable flag . On enabling the flag, user can write the grammar in *"Content Formatting Language" *in the content field. This will generate the randomized input message based on the given grammar. * * *"Content Formatting Language": *Structure of this language will be simple and intuitive even for the new user. And I know, this is the module on which I will be spending most of the development efforts to make it robust so that it will be compatible with all the input message format of the Middleware Applications. *JMeter After "Content Formatting Language":* JMeter is already robust and widely used. Addition of this module will focus the Middleware testers to have the combination of the test cases like functionality testing + Stress Testing + Performance Testing. *Development Duration: *Google Summer of code will motivate me to work on this module as full time intern of 4 months. Although the duration is 4 months, I will be giving support to this module for lifetime and keep contributing the new ideas. *Questions:* I request all of you, if you have any questions, suggestion, drawbacks about this idea then I would love to hear them and change the development plan accordingly.:) I would also love to hear the reviews of the perspective mentor of JMeter in GSOC 2013 on this module. Thank you very much. On Wed, Apr 3, 2013 at 12:14 PM, Noga <[email protected]> wrote: > If I understood you correctly:- > > 1. JMeter can already send messages to the middleware . > 2. JMeter can not send *meaningful messages* to the middleware. WHY? > 3. You want to > 1. Implement an add-on to make the messages meaningful? > 2. Or change some functionality such as to incorporate a language > string generator mechanism so that anyone can later incorporate the > language grammar to the engine, and generate strings on that > language? > 4. > > Please let us know which one option of 3.1 or 3.2 you want to build. > [3.2] IMHO might not be an easy task, language string generator generators > are never easy. > [3.1] Probably would not have any qualms. > > Thanks > --Noga > > > > On Wed, Apr 3, 2013 at 8:07 AM, Pranav Bhole <[email protected]> > wrote: > > > Hello to all, > > This is Pranav Bhole, I am Master student at The University of > > Texas at Dallas. I haven been using Jmeter extensively as core since 5-6 > > years in my academic and professional work. I worked for IBM in the > > Middleware Domain. Recently an idea came up in my mind with concern of > the > > following things: > > > > A. Jmeter sends the Bulk of Garbage message (of given size) in the given > > Queue. Internally, in the middleware application , this Queue is mostly > > linked with the Middleware Services which pick up the message and process > > it with the business logic. > > B. In the above case, if we wish to have performance harness test of the > > middleware application using Jmeter. Jmeter will simply push the Bulk > > Garbage message in the queue , this message will be straightforwardly > > rejected by the Service because it wont me matching with given input > > format of the service. > > > > With concern of the scenarios of A and B, I have an idea of implementing > > the Content Formatting Language for message contents. This language will > > send the formatted message in the Queue and which will be processed by > the > > service which pick up the message from the queue. In this way we could be > > able to push the meaning full messages in the Queue and eventually will > be > > able to analyze the performance harness of the entire Middleware > > Application. > > > > As I am graduate student, I wish to implement this module as student of > > Google Summer of Code 2013. > > I am pretty excited about the reviews of the Jmeter's developers > community > > on this idea. > > And off-course this is impossible without Jmeter Dev's prestigious > > guidance. I request to Jmeter's mentor to guide me about this. > > If you have any idea already running in your mind related to this then I > > would love to hear that. > > > > Thank you > > > > -- > > Pranav Bhole > > Student of MS in Computer Science for Fall 2012, > > University of Texas at Dallas > > http://www.linkedin.com/in/pranavbhole > > [email protected] > > Cell Phone No: 972-978-6108. > > > -- Pranav Bhole Student of MS in Computer Science for Fall 2012, University of Texas at Dallas http://www.linkedin.com/in/pranavbhole [email protected] Cell Phone No: 972-978-6108.
