ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » test cases

Post new topic  Reply to topic
 test cases « View previous topic :: View next topic » 
Author Message
mq_pm
PostPosted: Thu Nov 20, 2003 3:26 pm    Post subject: test cases Reply with quote

Centurion

Joined: 27 Aug 2003
Posts: 132

Hi,

Can anyone provide sample testcases. It is very urgent.

Thanks.
Back to top
View user's profile Send private message Send e-mail
TonyD
PostPosted: Thu Nov 20, 2003 5:03 pm    Post subject: Reply with quote

Knight

Joined: 15 May 2001
Posts: 540
Location: New Zealand

To test what?
Back to top
View user's profile Send private message Send e-mail
Missam
PostPosted: Fri Nov 21, 2003 7:08 am    Post subject: Reply with quote

Chevalier

Joined: 16 Oct 2003
Posts: 424

Don't be Urgent when you don't know what you want to test..
Back to top
View user's profile Send private message
JLRowe
PostPosted: Fri Nov 21, 2003 9:18 am    Post subject: Junit Reply with quote

Yatiri

Joined: 25 May 2002
Posts: 664
Location: South East London

I've used Junit to write unit tests for MQSI flows in Java. There is also another tool called DBUnit, which allows you to seed any databases with test data before each unit test.

A unit test for MQSI performs the following steps:

1) Check that no other processes have the queues open
2) Clear down the queues
3) Seed the database with test data
4) Put the input test message
5) Wait for output message(s)
6) Check output messages contain expected results
7) Check database contains expected results

If you have several flows chained together in the broker, then it is useful to define read & write aliases over each local queue. You can then have a unit test MQ environment configured to allow each flow to run individually, and a link test environment to test the whole chain of flows. (e.g)

Unit test:

LCLQ --> Flow1 --> LCLQ

LCLQ --> Flow2 --> LCLQ

Link test:

LCLQ --> Flow1 --> LCLQ --> Flow2 --> LCLQ

The basic aim of automated unit tests is to make it as easy as possible to run them. Then developers will run them often. Running the unit tests after you make each individual change to a flow boosts productivity and software quality no end.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » test cases
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.