| Testcase ID | Synopsis | Steps to Execute | Expected Results |
| WSRP_Event_001 | Single event portlet | 1. Create a LocalPortlet? which publishes the event 2. Create a Producer by adding a portlet which responds to the event generated by the portlet in step 1 3. Consume the above portlet 4. Publish the event by calling setEvent(Qname,Object) in the LocalPorltet? | The portlet consumed through Consumer should be able to process the event publised by the LocalPorltlet? |
| WSRP_Event_002 | Single event portlet with invalid argument | 1. Create a LocalPortlet? which publishes the event2. Create a Producer by adding a portlet which responds to the event generated by the portlet in step 13. Consume the above portlet4. Publish the event by calling setEvent(Wrong Qname,Object) in the LocalPorltet? | java.lang.IllegalArgumentException should be thrown |
| WSRP_Event_003 | Single event portlet with invalid argument | 1. Create a LocalPortlet? which publishes the event2. Create a Producer by adding a portlet which responds to the event generated by the portlet in step 13. Consume the above portlet4. Publish the event by calling setEvent(Null Qname,Object) in the LocalPortlet? | java.lang.IllegalArgumentException should be thrown |
| WSRP_Event_004 | Single event portlet with invalid argument | 1. Create a LocalPortlet? which publishes the event2. Create a Producer by adding a portlet which responds to the event generated by the portlet in step 13. Consume the above portlet4. Publish the event by calling setEvent( Qname,Null Object) in the LocalPortlet? | java.lang.IllegalArgumentException should be thrown |
| WSRP_Event_005 | Single event portlet with invalid argument | 1. Create a LocalPortlet? which publishes the event2. Create a Producer by adding a portlet which responds to the event generated by the portlet in step 13. Consume the above portlet4. Publish the event by calling setEvent( Qname,Object) Object different from declared in the LocalPortlet? | java.lang.IllegalArgumentException should be thrown |
| WSRP_Event_006 | Event Distirbution between two remote porltets | 1) Create a Producer with a portlet which publishes an Event2) Create another Producer with a portlet which responds to the event published3) Create two different consumers with the producers created in the above step4) Publish the event by calling setEvent(QName,Object) | The portlet consumed through Consumer should be able to process the event publised by the RemotePortlet? |
| WSRP_Event_007 | Event Distirbution between two remote porltets with invalid arguments | Repeat the steps as per WSRP_Event_002 to WSRP_Event_005 | Should work as per expected in these testcases |
| WSRP_Event_008 | Event Distirbution between two remote porltets with event response returning failure code | 1) Create a Producer with a portlet which publishes an Event2) Create another Producer with a portlet such that it throws a Runtime expecption(Error: Content not available)3) Create two different consumers with the producers created in the above step4) Publish the event by calling setEvent(QName,Object) to the portlet created in Step 2 | Consumer which publihes the event should not retry to dispatch the event |
| WSRP_Event_009 | Event Distribution between two remote portlets and event times out | 1) Create a Producer with a portlet which publishes an Event2) Create another Producer with a portlet such that it throws a Runtime expecption(Error: Content not available)3) Create two different consumers with the producers created in the above step4) Publish the event by calling setEvent(QName,Object) to the portlet created in Step 2 | Consumer should retry to send the event or proceed with another request |
| WSRP_Event_010 | Cyclic Event Distribution between two remote portlets | 1) Create two portlet which mutually pulishes and reponse to the events2) Create two producers with the portlets created in the above step3) Create two consumers for the two produers created in the above step4) Create two channels with the consumers created above5) Now publish the event by calling the setEvent(QName, Object) in these two remote protlets | The remoteportlets should respond and mutually handle the event |
| WSRP_Event_011 | Handling of System generated events by Remote Portlets | 1) Create a Producer with a portlet which publishes an Event2) Create another Producer with a portlet which responds to the event published3) Create two different consumers with the producers created in the above step4) Publish a System Generated event say Login or Logout event | Remote portlets should respond to the system generated events |
| WSRP_Event_012 | Handling of Wired Events by Remote portltes | 1) Create a portlet that gets the user's zip code and publish an event such that it sends this info to other portlets2) Create two portlets such that is respond the above event and renders the zip code3) Create two Producers with the portlets above4) Create two consumers based on the above Producers5) Deploy the portlet created in step 16) Enter the user's zip code and submit | Both remote portlets render the same zip code. Either one of the consumer should try to dispatch the zip code data to both the portlets |
| WSRP_Event_013 | Eventing with “default-event-namespace” defined in DD | Execute the above testcases with default-event-name | Results as above |