Thank you for your involvement. Yes, we are at the development stage when a JMS API client can be written, or at least, we're very close to that. Please look at the JMS Facade thread http://jboss.org/index.html?module=bb&op=viewtopic&t=61556, you'll see where we are. However, that client would have a very limited functionality. A lot of JMS API calls just throw NotYetImplementedException, so I am sure that at this stage, the client API won't pass any compliance test.
The client you used, even if it is functional, it is deprecated, so I would suggest not to start testing anything on it, since we'll drop that code anyway. Having someone who specializes compliance tests, or other kind of testing for that matter, is essential, so your help is more than welcome. I hope we'll have something that will start passing compliance tests in several weeks. Until then, I would like you to start thinking at a more conprehensive testing and benchmarking harness that will grow toghether with the project. This is what I have in mind: We'll have four kinds of tests: - unit tests: written by the developers, at the same time or before writing the code itself. "Old" XP principle. They are essential, since they'll catch regression bugs and we'll allow us to refactor more freely. - compliance tests: your stuff. Ideally, I don't want developers involved with them, they should be performed by someone who is not closely involved with the code (or not yet), just because his/her only concern is to see how solid is the implementation from the JMS point of view. - integration test: test how well our JMS provider integrates with the AS; mainly the QA team's job. - stress tests and benchmarks: I hope to have a benchmarking framework that will allow us to closely follow key metrics for our implementation. As a very quick example, I am thinking of something like: how does our implementation behave when one hundred producers concurrently send 10KB messages? What are the key metrics to follow? How do these metrics evolve from a release to another? Does our implementation scale? Are you interested in getting involved with that? How did you think of doing compliance tests? SpecJ? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870617#3870617 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870617 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
