| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Automated Testing of Message Flows |
« View previous topic :: View next topic » |
| Author |
Message
|
| ajomillar |
 Posted: Thu Jun 24, 2004 1:01 pm Post subject: Automated Testing of Message Flows |
 |
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| After attending the IBM T&M conference in Las Vegas, I began wondering what WMQI developers use for testing their message flows. Obviously, there is the manual approach: put a message to the input queue, get from the output queue, and compare to expected results. But what if there are many message types and even more message flows to test, especially with business rules? I suppose you could throw lots of people into the test effort. Do most people build their own test harness? If so, do you also build a unit test harness to test individual nodes? One vendor at the conference, Solstice Software, has a product automates the testing process. Any thoughts on this subject is appreciated. |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Jun 25, 2004 1:00 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
AJM,
good point!
first distinguish between development testing, i.e. a developper testing a new flow in development and
regression testing, i.e. a developper develivered a new flow which may impact other flows and they need to be tested.
for the first option you have several options like rfhutil, mqsiput etc.
testing and verifying is basically a manual task.
for the second I have collected input from the application teams a so called sample collection of input.
I have put these files with a name in an input directory,
amended a program called file2msg to put the filename in the correlid, run the files through the broker,
use amended msg2file which puts the output into a file with the same name with extension out in the out directory.
Manually verify the correctness of this output once.
Then copy the file to the verified directory.
Now the 'test' set and verified set is complete.
The next time someone changes something,
I re-run the test so the out directory gets filled again and
simply do a file compare to the respective file in the verified directory.
ofcourse this is only one way of doing this... I am sure there are many homegrown contact admin out there.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| JLRowe |
| Posted: Fri Jun 25, 2004 1:32 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| Junit is built into the v5 tooling, it's a unit test framework for java. I have also used DBunit, which allows you to seed a database before a unit test and check the contents after. |
|
| Back to top |
|
|
| TonyD |
| Posted: Fri Jun 25, 2004 4:54 pm Post subject: |
|
|
Knight
Joined: 15 May 2001
Posts: 540
Location: New Zealand
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
