How hard was it to run this test? I'd be interested to know what the compliance of MB1 was. It might be a good start to say we are aiming to meet the same bar.
Paul On 15 May 2012 09:34, Hasitha Hiranya <[email protected]> wrote: > Hi Srinath, > > There is a way to set filters according to JMSCTS documentation here. > http://jmscts.sourceforge.net/filter.html > > In that case I will be able to restrict the test under following criteria. > > > - *session* > > The *< session > *element specifies t he type of session message > acknowledgement behaviour to filter. Valid values for this element are: > - TRANSACTED > - AUTO_ACKNOWLEDGE > - DUPS_OK_ACKNOWLEDGE > - CLIENT_ACKNOWLEDGE > > - *destination* > > The *< destination > *element specifies the type of destination to > filter. Valid values for this element are: > - administered > - temporary > > - *deliveryMode* > > The *< deliveryMode > *element specifies the type of message delivery > mode to filter (as specified by javax.jms.DeliveryMode). Valid values for > this element are: > - PERSISTENT > - NON_PERSISTENT > > - *receiver* > > The *< receiver > *element specifies the type of message receiver to > filter. Valid values for this element are: > - asynchronous *- specifies asynchonous message receipt* > - synchronous *- specifies synchronous message receipt* > - asynchronous_durable *- specifies asynchronous message receipt by > durable topic subscribers* > - synchronous_durable *- specifies synchronous message receipt by > durable topic subscribers* > - browser *- speci fies queue browser receipt* > > - *message* > > The *< message > *element specifies the type of message (i.e. > javax.jms.Message) to filter. Valid values for this element are: > - BytesMessage > - MapMessage > - ObjectMessage > - StreamMessage > - TextMessage > > > By default all these variations are included in tests. I will check what > needs to be excluded. > > Thanks. > > > On Tue, May 15, 2012 at 10:59 AM, Srinath Perera <[email protected]> wrote: > >> Hi Hasitha, >> >> Can we remove some of the test? we need to categorize them as >> >> 1) Not applicable to us >> 2) Applicable but cannot be fixed >> 3) Applicable but can be fixed >> 4) Current working >> >> The we fix that we can, and leave others as TODOs etc. >> >> --Srinath >> >> >> On Tue, May 15, 2012 at 9:53 AM, Hasitha Hiranya <[email protected]>wrote: >> >>> Hi, >>> >>> I used JMSCTS [1] to test current MB (Actually Andes). I am attaching >>> the test results herewith. A few things to be noted. >>> >>> >>> - Some test failure happens as we do not allowed to delete >>> distributed queues yet. >>> - I could not run all the tests even if I allowed to run it from >>> 8.00 P.M to 7.00 A.M. I took a snapshot of reports while it was running. >>> - Test environment is* one node, clustering >>> enabled, OnceInOrderSupport disabled, Zookeeper and Cassandra servers are >>> externally running.* >>> - There are other issues like timeouts etc, which can be configured. >>> I used >>> >>> * >>> * >>> * >>> # Message receipt timeout >>> * >>> * >>> # The default time to wait for messages, in milliseconds >>> * >>> * >>> # >>> * >>> * >>> org.exolab.jmscts.core.MessagingBehaviour.timeout=2000 >>> ** * >>> >>> >>> >>> - I have also tested previous MB release to have a comparison and to >>> verify that I have set the test environment correctly. I am attaching >>> those >>> test results as well. >>> >>> >>> Note: test results html pages are linked to each other. Open >>> coverage.html to see overall results. >>> >>> Further, I'd like to know if we have to integrate JMSCTS with Andes. And >>> any idea how to overcome the problems we have with tests? Because as I can >>> see a lot has failed to various reasons. I have attached a part of the log >>> too (as it is too big to mail). >>> >>> >>> [1]. http://jmscts.sourceforge.net/ >>> >>> >>> Thank You. >>> >>> -- >>> *Hasitha Abeykoon* >>> Software Engineer; WSO2, Inc.; http://wso2.com >>> *cell:* *+94 719363063* >>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * >>> * >>> * >>> >>> >> >> >> -- >> ============================ >> Srinath Perera, Ph.D. >> Senior Software Architect, WSO2 Inc. >> Visiting Faculty, University of Moratuwa >> Member, Apache Software Foundation >> Research Scientist, Lanka Software Foundation >> Blog: http://srinathsview.blogspot.com/ >> Photos: http://www.flickr.com/photos/hemapani/ >> Phone: 0772360902 >> > > > > -- > *Hasitha Abeykoon* > Software Engineer; WSO2, Inc.; http://wso2.com > *cell:* *+94 719363063* > *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * > * > * > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Paul Fremantle CTO and Co-Founder, WSO2 OASIS WS-RX TC Co-chair, VP, Apache Synapse UK: +44 207 096 0336 US: +1 646 595 7614 blog: http://pzf.fremantle.org twitter.com/pzfreo [email protected] wso2.com Lean Enterprise Middleware Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
