Excellent work Maninda. Tests are passing now.

Results :

Tests run: 20, Failures: 0, Errors: 0, Skipped: 0

[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WSO2 BAM Integration .............................. SUCCESS [0.869s]
[INFO] WSO2 BAM - Integration Test ....................... SUCCESS
[9:27.762s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9:29.680s
[INFO] Finished at: Thu May 16 13:02:57 IST 2013
[INFO] Final Memory: 22M/81M
[INFO]
------------------------------------------------------------------------

On Tue, May 14, 2013 at 1:02 PM, Maninda Edirisooriya <[email protected]>wrote:

> Yes. I am looking into this.
>
> *
> Maninda Edirisooriya*
> Software Engineer
> *WSO2, Inc.
> *lean.enterprise.middleware.
>
> *Blog* : http://maninda.blogspot.com/
> *Phone* : +94 777603226
>
>
> On Tue, May 14, 2013 at 1:00 PM, Tharindu Mathew <[email protected]>wrote:
>
>> Hi Maninda,
>>
>> Please take over this. The test suite has to pass for us to release.
>>
>>
>> On Tue, May 14, 2013 at 12:20 PM, Krishantha Samaraweera <
>> [email protected]> wrote:
>>
>>> There are so many reasons that could cause this behavior. Most probably
>>> test cases are inter dependent. As a convention changes done to BAM server
>>> should be wipe out at the end of each test case. You can verify what is
>>> really happening by setting a debug point in your test class and running
>>> the all suite.
>>>
>>> mvn install -Dmaven.surefire.debug would help
>>>
>>> BTW, have you guys added new test cases recently in to BAM ? because we
>>> haven't change the auto framework except dependencies and this behavior
>>> could have caused by newly added tests.
>>>
>>> Thanks,
>>> Krishantha.
>>>
>>> On Tue, May 14, 2013 at 12:02 PM, Tharindu Mathew <[email protected]>wrote:
>>>
>>>> Hi,
>>>>
>>>> In the BAM integration test suite, there is a test which fails when the
>>>> whole integration suite is run. See at [0].
>>>>
>>>> But, when this test case is run individually, it succeeds. See [1] for
>>>> details.
>>>>
>>>> This is reproducible. Why does this happen? How can we avoid this?
>>>>
>>>>
>>>> [0] -
>>>>
>>>> Tests run: 18, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>>>> 472.591 sec <<< FAILURE!
>>>> [2013-05-14 11:42:22,878]  INFO
>>>> {org.wso2.carbon.integration.framework.utils.ServerUtils} -  Shutting down
>>>> server...
>>>>
>>>> Results :
>>>>
>>>> Failed tests:
>>>> publishConcurrentEvents(org.wso2.bam.integration.tests.reciever.BAMReceiverVariableFieldsTestCase):
>>>> Actual Events sent and the saved events are different expected:<true> but
>>>> was:<false>
>>>>
>>>> Tests run: 18, Failures: 1, Errors: 0, Skipped: 0
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] WSO2 BAM Integration .............................. SUCCESS
>>>> [0.402s]
>>>> [INFO] WSO2 BAM - Integration Test ....................... FAILURE
>>>> [8:01.509s]
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] BUILD FAILURE
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 8:02.478s
>>>> [INFO] Finished at: Tue May 14 11:42:23 IST 2013
>>>> [INFO] Final Memory: 22M/81M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>>
>>>>
>>>> [1] -
>>>>
>>>> $ mvn test -Dtest="*TestServer*,BAMReceiver*"
>>>>
>>>> [INFO] Scanning for projects...
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Reactor Build Order:
>>>> [INFO]
>>>> [INFO] WSO2 BAM Integration
>>>> [INFO] WSO2 BAM - Integration Test
>>>> [INFO]
>>>>
>>>> *<snip/>*
>>>>
>>>> Results :
>>>>
>>>> Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
>>>>
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Reactor Summary:
>>>> [INFO]
>>>> [INFO] WSO2 BAM Integration .............................. SUCCESS
>>>> [0.399s]
>>>> [INFO] WSO2 BAM - Integration Test ....................... SUCCESS
>>>> [1:53.060s]
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] BUILD SUCCESS
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Total time: 1:54.008s
>>>> [INFO] Finished at: Tue May 14 11:52:34 IST 2013
>>>> [INFO] Final Memory: 22M/81M
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> mackies-mac:integration mackie$
>>>>
>>>>
>>>> --
>>>> Regards,
>>>>
>>>> Tharindu Mathew
>>>>
>>>> Associate Technical Lead, WSO2 BAM
>>>> Member - Data Mgmt. Committee
>>>>
>>>> blog: http://tharindumathew.com/
>>>> M: +94777759908
>>>>
>>>> _______________________________________________
>>>> Dev mailing list
>>>> [email protected]
>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev
>>>>
>>>>
>>>
>>
>>
>> --
>> Regards,
>>
>> Tharindu Mathew
>>
>> Associate Technical Lead, WSO2 BAM
>> Member - Data Mgmt. Committee
>>
>> blog: http://tharindumathew.com/
>> M: +94777759908
>>
>
>


-- 
Regards,

Tharindu Mathew

Associate Technical Lead, WSO2 BAM
Member - Data Mgmt. Committee

blog: http://tharindumathew.com/
M: +94777759908
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to