Re: [Dev] MB test cases improvements - check message counts

[Hasitha Hiranya]

For example following scenario should be testable. At least check message
counts after sending to DLC/deleting/purging operations

1) Send couple of messages to MBQ1 queue. Make these messages end up in DLC

2) Disable the JMS consumer and send messages so that there will be message
in MBQ1 queue.

3) Purge the MBQ1 ( so that messages in DLC and MBQ1 will be cleared)

4) Send messages to MQ1 again ...

5) Enable JMS Consumer (this will put messages to dlc again)

6) Browse the Queue you will see there are message in DLC and the queue and
verify queue count=0 dlc count = x

On Tue, Jan 27, 2015 at 9:01 PM, Hasitha Hiranya  wrote:

> Hi,
>
> We need to be careful with message count display in UI in MB 3.0.0.
>
> For most of users this is the first impression about the product. If
> message counts are wrong and unpredictable, even for us developers, it is
> hard to isolate issues.
>
> Thus in the test suite via admin services we should be able to query the
> message count after doing some message publish/ consume.
>
> We need to add some tests (or do this at the end of each existing test
> standalone and cluster) checking message count and verify.
>
> Thanks
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


-- 
*Hasitha Abeykoon*
Senior Software Engineer; WSO2, Inc.; http://wso2.com
*cell:* *+94 719363063*
*blog: **abeykoon.blogspot.com* 
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB test cases improvements - check message counts

[Ramith Jayasinghe]

awsome idea.
lets do that.

On Tue, Jan 27, 2015 at 4:36 PM, Hasitha Hiranya  wrote:

> For example following scenario should be testable. At least check message
> counts after sending to DLC/deleting/purging operations
>
> 1) Send couple of messages to MBQ1 queue. Make these messages end up in
> DLC
>
> 2) Disable the JMS consumer and send messages so that there will be
> message in MBQ1 queue.
>
> 3) Purge the MBQ1 ( so that messages in DLC and MBQ1 will be cleared)
>
> 4) Send messages to MQ1 again ...
>
> 5) Enable JMS Consumer (this will put messages to dlc again)
>
> 6) Browse the Queue you will see there are message in DLC and the queue
> and verify queue count=0 dlc count = x
>
> On Tue, Jan 27, 2015 at 9:01 PM, Hasitha Hiranya 
> wrote:
>
>> Hi,
>>
>> We need to be careful with message count display in UI in MB 3.0.0.
>>
>> For most of users this is the first impression about the product. If
>> message counts are wrong and unpredictable, even for us developers, it is
>> hard to isolate issues.
>>
>> Thus in the test suite via admin services we should be able to query the
>> message count after doing some message publish/ consume.
>>
>> We need to add some tests (or do this at the end of each existing test
>> standalone and cluster) checking message count and verify.
>>
>> Thanks
>>
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
>
> --
> *Hasitha Abeykoon*
> Senior Software Engineer; WSO2, Inc.; http://wso2.com
> *cell:* *+94 719363063*
> *blog: **abeykoon.blogspot.com* 
>
>


-- 
Ramith Jayasinghe
Technical Lead
WSO2 Inc., http://wso2.com
lean.enterprise.middleware

E: ram...@wso2.com
P: +94 777542851
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] MB test cases improvements - check message counts

[Shammi Jayasinghe]

Hi MB Team,

+1, I wish if we can do all about in Single setup and a Clustered Setup
with ESB or one of the other products integration. Because practically no
one is going to deploy MB alone and most of the time people go for a
clusters setup with failover scenario. In the same case please check this
with various message sizes and high message counts at least beginning from
10 messages to 1 million messages with both Topic and Queue Scenarios.

Thanks
Shammi

On Tue, Jan 27, 2015 at 10:39 AM, Ramith Jayasinghe  wrote:

> awsome idea.
> lets do that.
>
> On Tue, Jan 27, 2015 at 4:36 PM, Hasitha Hiranya 
> wrote:
>
>> For example following scenario should be testable. At least check message
>> counts after sending to DLC/deleting/purging operations
>>
>> 1) Send couple of messages to MBQ1 queue. Make these messages end up in
>> DLC
>>
>> 2) Disable the JMS consumer and send messages so that there will be
>> message in MBQ1 queue.
>>
>> 3) Purge the MBQ1 ( so that messages in DLC and MBQ1 will be cleared)
>>
>> 4) Send messages to MQ1 again ...
>>
>> 5) Enable JMS Consumer (this will put messages to dlc again)
>>
>> 6) Browse the Queue you will see there are message in DLC and the queue
>> and verify queue count=0 dlc count = x
>>
>> On Tue, Jan 27, 2015 at 9:01 PM, Hasitha Hiranya 
>> wrote:
>>
>>> Hi,
>>>
>>> We need to be careful with message count display in UI in MB 3.0.0.
>>>
>>> For most of users this is the first impression about the product. If
>>> message counts are wrong and unpredictable, even for us developers, it is
>>> hard to isolate issues.
>>>
>>> Thus in the test suite via admin services we should be able to query the
>>> message count after doing some message publish/ consume.
>>>
>>> We need to add some tests (or do this at the end of each existing test
>>> standalone and cluster) checking message count and verify.
>>>
>>> Thanks
>>>
>>> --
>>> *Hasitha Abeykoon*
>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>> *cell:* *+94 719363063*
>>> *blog: **abeykoon.blogspot.com* 
>>>
>>>
>>
>>
>> --
>> *Hasitha Abeykoon*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>> *cell:* *+94 719363063*
>> *blog: **abeykoon.blogspot.com* 
>>
>>
>
>
> --
> Ramith Jayasinghe
> Technical Lead
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> E: ram...@wso2.com
> P: +94 777542851
>
>


-- 
Best Regards,

*  Shammi Jayasinghe*
Associate Tech Lead
WSO2, Inc.; http://wso2.com,
mobile: +1-812-327-3505
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev