We also need some core integration tests that test the new browsing implementation. This is a general thing when writing new stuff on core - we need integration tests. As I mentioned before don't worry too much about the easymock tests, they're not so important. For browsing I would expect to see: Browsing with and without selectors. Verifying messages don't get acknowledged Browsing with multiple browsers on same queue Verifying calling acknowledge on message does nothing etc Replication with browsing is also currently broke, although this will be hard to get it working with the copying technique - we'll have to wait for the iterator for that. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4183059#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...