Hello JMeter users! Just wanted to ask about testing 'publish-subscribe' applications - like those used in EAI (enterprise application integration) systems and message queues.
Here's a couple of likely test scenarios: ------------------------ System A published Document1 - 5 systems subscribed (systems B,C,D,E,F) System M published Document1 - 7 systems subscribed (systems D,E,F,G,H,I,J) ------------------------ In the scenarios above, we need to test that each document published got to all destination systems that subscribed to it. This is the type of test structure I had in mind: one toplevel testcase for each document published by a system - it uses include controllers to string-in subscribe-checking functionality for destination systems, thus avoid code duplication across JMXs. For the 2 scenarios above: ------------------------ TESTCASE 1 ----------- System A published Document1 Include controller: check Document1 on system B ... Include controller: check Document1 on system F TESTCASE 2 ----------- System M published Document1 Include controller: check Document1 on system D ... Include controller: check Document1 on system J ------------------------ In any case, I'd appreciate some feedback about this. I've run into problems with the include controller (see my previous email to list today), so perhaps people use different approach to test EAI systems... Regards Sonam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
